[Zope-CMF] user identity crisis - proxy server cache problem?

[Shane Hathaway]

Kari-Hans Kommonen wrote:
> Could it be that there is a proxy server in their network somehow 
> messing things up? Is it something else? Is there a way to fight these 
> kinds of problems from the zope server side?

TCPWatch is designed to help in just this kind of situation.  Download 
TCPWatch:

http://hathaway.freezope.org/Software/TCPWatch

Run it like this:

python tcpwatch.py -p 3128

(Use -s if you don't have Tkinter installed.  Use -r to log to a 
directory if -s produces too much data.)

Then change your user's proxy settings to point to your proxy.  Look to 
see if the browser sends the cookie or not.  If the browser is sending 
the cookie but Zope isn't getting it, use TCPWatch on the server side. 
If Zope is running on port 8080, do this on the same box running Zope:

python tcpwatch.py -L 8090:localhost:8080

Then ask your user to use port 8090 instead of 8080 to access Zope.

Shane