Except that not specifying a path and specifying a path of "/" should be the same thing, according to the CGI.pm documentation, but they are clearly not.
On 6/6/06, Rob Kinyon <[EMAIL PROTECTED]> wrote:
This sounds like a Safari bug, as amazing as that sounds. :-) (Safari may be doing the right thing and everyone else has created a looser de facto standard - this has been known to happen.) Rob On 6/6/06, Joel Gwynn <[EMAIL PROTECTED]> wrote: > I can't believe there could be a bug in CGI.pm, but I'm experiencing > some strange behavior with cookie paths. My brother was trying to log > into my app using Safari, and he couldn't log in. Other browsers are > fine. So I figured there was a cookie path problem; when I created > the cookie I didn't set a path. Once I gave it a path "/", he could > log in just fine. My question is this. According to the > documentation: > > -path points to a partial URL on the current server. The cookie will > be returned to all URLs beginning with the specified path. If not > specified, it defaults to '/', which returns the cookie to all pages > at your site. > > The path is supposed to be set to "/" by default, but apparently not. > What am I missing? > > --------------------------------------------------------------------- > Web Archive: http://www.mail-archive.com/[email protected]/ > http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
--------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[email protected]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
