Databases
StackOverflow2013
Postsdbo
POSession not saving when moving from ssl to non-ssl
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSession not saving when moving from ssl to non-ssl
    primarykey
    data
    text
    <p>I have a login screen that I force to be ssl, so like this: <a href="https://www.foobar.com/login" rel="noreferrer">https://www.foobar.com/login</a> then after they login, they get moved to the homepage: <a href="https://www.foobar.com/dashbaord" rel="noreferrer">https://www.foobar.com/dashbaord</a></p> <p>However, I want to move people off of SSL once logged in (to save CPU), so just after checking that they are in fact logged in on <a href="https://www.foobar.com/dashbaord" rel="noreferrer">https://www.foobar.com/dashbaord</a> I move them to <a href="http://www.foobar.com/dashbaord" rel="noreferrer">http://www.foobar.com/dashbaord</a></p> <p>Well this always seems to wipe out the session variables, because when the page runs again, it confirms they are logged in (as all pages do) and session appears not to exist, so it moves them to the login screen.</p> <p>Oddness/findings:</p> <ol> <li>List item</li> <li>The second login always works, and happily gets me to <a href="http://www.foobar.com/dashbaord" rel="noreferrer">http://www.foobar.com/dashbaord</a></li> <li>It successfully creates a cookie the first login</li> <li>If I login twice, then logout, and login again, I don't need two logins (I seem to have traced this to the fact that the cookie exists). If I delete the cookie, I'm back to two logins.</li> <li>After the second login, I can move from non-ssl from ssl and the session persists.</li> <li>On the first login, the move to the non-ssl site wipes out the session entirely, manually moving back to the ssl site still forces me to login again.</li> <li>The second login using the exact same mechanism as the first, over ssl</li> </ol> <p>What I tried:</p> <ol> <li>Playing with Cake's settings for security.level and session.checkagent - nothing</li> <li>Having cake store the sessions in db (as opposed to file system) - nothing</li> <li>Testing in FF, IE, Chrome on an XP machine.</li> </ol> <p>So I feel like this is something related to the cookie being created but not being read. </p> <p>Environment: 1. Debian 2. Apache 2 3. Mysql 4 4. PHP 5 5. CakePHP 6. Sessions are being saved PHP default, as files</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJustin
    1. USJustin
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSession not saving when moving from ssl to non-ssl
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POSession not saving when moving from ssl to non-ssl
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POSession not saving when moving from ssl to non-ssl
      1. USMatty
      1. VTFavorite
    1. COOK, I was wrong about this not affecting IE. I wasn't properly clearing cache in IE.
      singulars
      1. POSession not saving when moving from ssl to non-ssl
      1. USJustin
    2. COSee also: http://stackoverflow.com/questions/7969719/cakephp-cookie-session-problems
      singulars
      1. POSession not saving when moving from ssl to non-ssl
      1. USJari Keinänen
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload