cookie_debugging

This is part of The Pile, a partial archive of some open source mailing lists and newsgroups.



Subject: Re: Apache, Mod_Perl and Custom Access/Authentication
From: Drew Taylor <dtaylor@vialogix.com>
Date: Fri, 09 Jun 2000 09:37:36 -0400

Steffers wrote:
> 
> On the downside, i +still+ cant get the cookies to work,
> although after faking a session via telnet it seems to work
> jst fine. Set-Cookie and everything. It +seems+ to be setting
> the cookie, but Apache is claiming that the browser doesnt
> like them (and yes, i have double checked that cookies are
> enabled on our netscape clients ;). I think its probably something
> to do with the layout of the servers dirctories. FeH!

One last thing: have you checked the path being sent with the cookie? I
always use '/', so the browser always sends it back. Domain & Path are
the two critical factors in cookies. Could you post the result HTTP
headers for perusal?

===

Subject: Re: Apache, Mod_Perl and Custom Access/Authentication
From: Drew Taylor <dtaylor@vialogix.com>
Date: Fri, 09 Jun 2000 09:46:43 -0400


Vegard Vesterheim wrote:
>  
> When dealing with cookie problems, it can be helpful to use a 'HTTP
> protocol sniffer'. You configure your browser to use the sniffer as a
> proxy, which will be sitting between the server and The client and
> allows you to 'listen in' on the HTTP conversation.
> 
> There are probably a lot of tools that can do this, I have used
> wsnitch which has a nice GTK-based UI, and a perl script (webproxy.pl)
> made by Randal Schwartz.

Wsnitch looks very cool. I'm going to give it a try right now. I like
the fact that I can still use the browser AND see the raw headers. :-) 
BTW, google took me right to wsnitch's homepage using the "I feel lucky"
option. Google rocks!

===


the rest of The Pile (a partial mailing list archive)

doom@kzsu.stanford.edu