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 ;-) But I'd forgotten to put the / there, and assumed the browser would assume this if no / was passed to it. However they don't, so I was suggesting that if a Cookie has no path set then one should be written by default as a totally useless header is currently written in the form: Set-Cookie: someName=someValue; expires.... and due to the lack of a path, every browser ignores it. > > peter > > John Baker wrote: > > It appears if you don't set a path on the cookie (setPath), it doesn't > > default to anything and therefore doesn't place anything in the response > > header. Browsers then ignore it ;-) > > > > Perhaps Cookie by default should have a path of /. > > > > John > > > > -- > > John Baker, BSc CS. > > Java Developer, TEAM/Slb. http://www.teamenergy.com > > Views expressed in this mail are my own. > > > > -- > > To unsubscribe, e-mail: > > <mailto:[EMAIL PROTECTED]> For additional > > commands, e-mail: <mailto:[EMAIL PROTECTED]> -- John Baker, BSc CS. Java Developer, TEAM/Slb. http://www.teamenergy.com Views expressed in this mail are my own. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
