CodeIgniter Session Problems Thread

[eluser]jedd[/eluser]
[quote author="mrbinky3000" date="1258787584"]So, to recreate.

- Grab CI, install it
- Grab dx_auth, install it.
- Config both
- Log in with Firefox. No problems.
- Try and login using IE. No go.
[/quote]

Okay, I've done as you directed.

I grabbed the current production release of CodeIgniter, and dx_auth. I configured both. I logged in with konqueror and Firefox/Iceweasel and proved out that I could get to the backend screens (as admin).

I cranked up a virtual machine running a pristine new install of XP with IE v6.

And guess what? It works!

Or, if you prefer - go.

There has to be something special about your environment. Curiously this is what people have been telling you for some time, though you seem disinclined to work towards a solution.

My environment :
Debian unstable with Linux 2.6.30
KDE 4.3.2
Virtual machine:
VirtualBox running XP SP3 with IE6
URL:
http://192.168.1.100/~jedd/binky/

Importantly I have no underscores in my hostname - is this something that has been consistent in your previous problem sites?

My VirtualBox XP environment picks up the (adjusted) time from the localhost, so it's accurate to within a couple of seconds. Have you confirmed with your previous problem sites that the time was in sync (or at least very close to being so)?

I mention time and underscores as they appear to be the two common things people have suggested you check - though you have yet to usefully comment whether they apply on your site(s).

Perhaps you could crank up an instance of a broken CI / dx_auth system - tarball it and make it available for me to play with? I suspect there's not much benefit there - since I've just pulled these things in from public sources and then did minimal configuration work against them - but just to rule it out. Setting up a VM is a much bigger task, especially as it appears to be a client-end problem.

Are you seeing entries appear in the ci_session table at all? Analysing the contents of those might help in narrowing down if it's a time-based problem. Similarly bumping up the session life to something large (48 hours or so).

I think you just need to start spilling on the details of your environment, if you genuinely want anyone to be able to help you solve this problem.