I have a mysterious mistaken identity problem that I have not been
able to solve.
There are two common sources of this problem. One is an ID generation
system that is not unique enough. Another is a bug in your code with
globals (see the section of the Guide about debugging with httpd -X).
Although all your cookies will be probably be going to the same proxy for
those requests from the same isp, the tcp-ip session will remain the same
and it is most likely that you'll still be connected to the same ip which
made the initial proxy connection. My thought is possibly that you're
Perrin Harkins wrote:
002801c1b63b$2563aea0$18020c0a@PerriHar">
I have a mysterious "mistaken identity" problem that I have not beenable to solve.
There are two common sources of this problem. One is an ID generationsystem that is not unique enough. Another is a bug in your
2. I don't think it's a global vairable issue. Basically, I just grab
the cookie by $r-header_in('Cookie')
and decrypt it.
It's what you do after that that matters.
Besides, if it's global then the mistaken ID's should
be from anywhere randomly.
True, but random may not always look
small operations. I'm pretty convinced that the problem is on their
end. My theory is that these proxies may have cached the cookie
with an IP address which they provide their clients.
Have you tried capturing all ethernet packets and seeing if the raw
data supports this conclusion.
Perrin Harkins wrote:
009001c1b65b$068df3d0$18020c0a@PerriHar">
2. I don't think it's a global vairable issue. Basically, I just grabthe cookie by $r-header_in('Cookie')and decrypt it.
It's what you do after that that matters.
All it does is get the user login info and
On Fri, 15 Feb 2002, Rob Nagler wrote:
small operations. I'm pretty convinced that the problem is on their
end. My theory is that these proxies may have cached the cookie
with an IP address which they provide their clients.
Have you tried capturing all ethernet packets and seeing if
Dzuy Nguyen wrote:
I have been getting many reports from our users that they have been
mistakenly identified as someone else.
I have tried to login as that user and just can't re-create the problem
and I can't be at their computer to
diagnose it. One thing I'm pretty sure about is that
