in reply to Re^2: CGI Cookie Inconsistencies
in thread CGI Cookie Inconsistencies

It might not be the/a problem but I can see it dropping the other headers while doing a redispatch depending on the engine. This issue caused an extremely bizarre and maddeningly difficult bug in some modperl I worked on once (it would execute an entirely unrelated handler on some relative redirects). The point here being, it's wrong as is and when you break standards you get unspecified behavior whether or not it's causing the bug your users are reporting. Try patching it. Verify it's reasonable in your own environment (I didn't test it though I've done a lot of this stuff) then push it out to a user who is seeing the bug and get some feedback.

Replies are listed 'Best First'.
Re^4: CGI Cookie Inconsistencies
by ranqor (Initiate) on Nov 05, 2009 at 06:03 UTC
    I know exactly what you mean about the standards thing, especially in IE. I've got the code updated using the proper URI. I'll report back in the am when I've heard back from the users.
[reply]
      Nope, didn't help :\ One of the users who couldn't initially save cookies and login can access it from a different computer in the home successfully. Now I've got 2 more people having the same issue though. I'm stumped.
[reply]

        Next things to try might be domain and path; it looks like you're not setting them. Still just guesses and it seems increasingly unlikely that it's the actual cookie that's the problem.

        Best thing would be to try to get a *detailed* report of the exact steps that trigger it from an affected user. Including whatever Wireshark (or Live HTTP Headers or Fiddler or something) log for the entire process.

[reply]
        Try provide special link "got trouble logging in, click here" which logs to special file as much info as possible.
[reply]

In Section Seekers of Perl Wisdom