[eluser]skunkbad[/eluser]
So, is this only a problem when there are multiple ajax requests going on at the same time? I've never noticed any problems like sessions dropping for no reason, but my ajax usage is usally limited to one request at a time. Even when using the database to store CI sessions, you still have a session cookie as an identifier. It seems strange that nobody has ever fixed this. Sounds like it qualifies as a bug.
I've noticed that there are identical names for cookies to be set in the CI session, but never noticed that multiple cookies are set:
Code:
Set-Cookie: communityAuth=knu9s+laUsjy5yRBotw; path=/
communityAuth=1LdeyBDh8DFz0zwB6hw; path=/
communityAuth=H05qYyLqOjv6LRUVj; path=/
communityAuth=jUnxm+aiGuN6HTpmi; path=/