if you want the cookies to be readable by all pages, you should set it
to /. That's standard practice. Also, if you have multiple webserver
with names like www1, www2, www3., you should also set the cookie to
use yourbiz.com.
peter
John Baker wrote:
It appears if you don't set a path
On Monday 01 July 2002 12:59, peter lin wrote:
if you want the cookies to be readable by all pages, you should set it
to /. That's standard practice. Also, if you have multiple webserver
with names like www1, www2, www3., you should also set the cookie to
use yourbiz.com.
I know this
that's the problem with assumptions :)
Actually I believe the W3C spec says the path will default to directory
the pages resides in. So that page /hello/greeting.jsp will have
/hello as the path. Only files under /hello can read the cookie.
Atleast that's my understanding of how cookie path is
On Monday 01 July 2002 13:16, peter lin wrote:
that's the problem with assumptions :)
Actually I believe the W3C spec says the path will default to directory
the pages resides in. So that page /hello/greeting.jsp will have
/hello as the path. Only files under /hello can read the cookie.
http://wp.netscape.com/newsref/std/cookie_spec.html
OR
http://www.ietf.org/rfc/rfc2109.txt
OR
http://www.ietf.org/rfc/rfc2965.txt
PATH=path
Optional. The Path attribute specifies the subset of URLs to which this
cookie applies.
John Baker wrote:
On Monday 01 July 2002 13:16, peter lin
On Monday 01 July 2002 13:29, Tim Funk wrote:
http://wp.netscape.com/newsref/std/cookie_spec.html
OR
http://www.ietf.org/rfc/rfc2109.txt
OR
http://www.ietf.org/rfc/rfc2965.txt
PATH=path
Optional. The Path attribute specifies the subset of URLs to which this
cookie applies.
But as
John Baker wrote:
Well a reliable source tells me that there is no w3c spec for Cookies, and
infact the concept was conjured by Netscape. There is an RFC spec for
Cookies, but it's largely ignored.
So as the useful browsers out there ignore Cookie requests without a path, it
might be
On Monday 01 July 2002 13:38, peter lin wrote:
John Baker wrote:
Well a reliable source tells me that there is no w3c spec for Cookies,
and infact the concept was conjured by Netscape. There is an RFC spec for
Cookies, but it's largely ignored.
So as the useful browsers out there
is not working in the same manor that you did and
can fix it.
-Original Message-
From: John Baker [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 01, 2002 8:33 AM
To: Tomcat Developers List
Subject: Re: That Cookie thing
On Monday 01 July 2002 13:29, Tim Funk wrote:
http://wp.netscape.com
for providing
such a sensible warning.
John
-Original Message-
From: John Baker [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 01, 2002 8:33 AM
To: Tomcat Developers List
Subject: Re: That Cookie thing
On Monday 01 July 2002 13:29, Tim Funk wrote:
http://wp.netscape.com/newsref/std
]]
Sent: Monday, July 01, 2002 8:33 AM
To: Tomcat Developers List
Subject: Re: That Cookie thing
On Monday 01 July 2002 13:29, Tim Funk wrote:
http://wp.netscape.com/newsref/std/cookie_spec.html
OR
http://www.ietf.org/rfc/rfc2109.txt
OR
http://www.ietf.org/rfc/rfc2965.txt
[mailto:[EMAIL PROTECTED]]
Sent: Monday, July 01, 2002 8:33 AM
To: Tomcat Developers List
Subject: Re: That Cookie thing
On Monday 01 July 2002 13:29, Tim Funk wrote:
http://wp.netscape.com/newsref/std/cookie_spec.html
OR
http://www.ietf.org/rfc/rfc2109.txt
On Mon, 1 Jul 2002, John Baker wrote:
Date: Mon, 1 Jul 2002 13:20:31 +0100
From: John Baker [EMAIL PROTECTED]
Reply-To: Tomcat Developers List [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Subject: Re: That Cookie thing
On Monday 01 July 2002 13:16, peter lin wrote
13 matches
Mail list logo
