Databases
StackOverflow2013
Postsdbo
POCodeigniter confilcting sessions behind proxy
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCodeigniter confilcting sessions behind proxy
    primarykey
    data
    text
    <p>We have a web applications that have just gone live. As this is used on several corporate networks, a peculiar issue has come up. </p> <p>Users are able to login into the system but users that are behind corporate networks intermittently get logged in/view other users profiles as their own. Esentially the sessions are colliding. </p> <p>These are the current settings on the server :</p> <pre><code>$config['sess_cookie_name'] = 'cisession'; $config['sess_expiration'] = 72000; $config['sess_expire_on_close'] = FALSE; $config['sess_encrypt_cookie'] = FALSE; $config['sess_use_database'] = FALSE; $config['sess_table_name'] = 'ci_sessions'; $config['sess_match_ip'] = FALSE; $config['sess_match_useragent'] = TRUE; $config['sess_time_to_update'] = 300; </code></pre> <p>We are on amazon behind a load balancer on a LAMP stack.</p> <p>We're really pulling our hair on this one, any pointers are welcome. Thanks!</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. UScodeHead
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POCodeigniter confilcting sessions behind proxy
      1. USJamesT
      1. VTFavorite
    2. VO
      singulars
      1. POCodeigniter confilcting sessions behind proxy
      1. USAjeet Sinha
      1. VTFavorite
    3. VO
      singulars
      1. POCodeigniter confilcting sessions behind proxy
      1. This table or related slice is empty.
      1. VTDownMod
    1. COYou might want to try asking on http://serverfault.com/ and include details on what the topology is (proxies, etc) on both sides. This sounds like an issue on the network layer and not a programmatic issue. A quick google search brought up http://aws.amazon.com/about-aws/whats-new/2010/04/08/support-for-session-stickiness-in-elastic-load-balancing/ which talks about sticky sessions. Basically, if you're using a load balancer with multiple servers behind it, there has to be a mechanism to "stick" the session to the server that originated the session.
      singulars
      1. POCodeigniter confilcting sessions behind proxy
      1. USstormdrain
    2. COThe issue is happening across at least 4 such types of networks, so I would rule out this at this point. Also sticky session comes into play so the same users stick to the same server instance on amazon. Appriciate your taking the time, but, i think its something on the application and session handling thats causing this.
      singulars
      1. POCodeigniter confilcting sessions behind proxy
      1. UScodeHead
    3. COYes, that would make sense that it were happening across multiple networks if the sessions aren't sticky; there isn't anything telling the balancer which server to send the request to. So user 1 starts a session on server 1; user 2 starts a session on server 2; user 1's next request goes to server 2 and gets user 2's session. If you haven't made any other modifications to codeigniters sessions, codeigniter is NOT the problem otherwise this issue would pop up for everyone that uses CI.
      singulars
      1. POCodeigniter confilcting sessions behind proxy
      1. USstormdrain
 

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