W3C home > Mailing lists > Public > www-jigsaw@w3.org > January to February 1997

Cookies & Netscape

From: Brian Millett <bpm@techapp.com>
Date: Wed, 19 Feb 1997 18:07:28 -0600
To: www-jigsaw@w3.org
Message-ID: <19970220000728.AAA11572@vlad.terraweb.com>
Anselm,
	I read the draft on http state management and yes the way to send
multiple Cookies is with a comma separated list of cookies.  However
Netscape 3.01 does not process this protocol correctly.  If the cgi
sends the following headers:

 
HTTP/1.0 200 OK
MIME-Version: 1.0
Set-Cookie: uid=fred; path=/,pwd=foo; path=/
Content-type: text/html

Then Netscape sends back to the server the following:

11116 STDIN(REQ): POST /cgi-bin/test-cookie HTTP/1.0

11116 STDIN(HEADERS): Referer: http://vlad:8080/cgi-bin/test-cookie
11116 STDIN(HEADERS): Connection: Keep-Alive
11116 STDIN(HEADERS): User-Agent: Mozilla/3.01Gold (X11; U; SunOS 5.4 sun4m)
11116 STDIN(HEADERS): Host: vlad:8080
11116 STDIN(HEADERS): Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*
11116 STDIN(HEADERS): Cookie: uid=fred
11116 STDIN(HEADERS): Content-type: application/x-www-form-urlencoded
11116 STDIN(HEADERS): Content-length: 0
11116 STDIN(HEADERS): 

The Cookie: uid=fred is not correct.

So my question is, should Jigsaw be backward compatible?  Or should I
just plan on it not working until Netscape fixes their browser?

Thanks

-- 
Brian Millett                    
Technology Applications Inc.     "Heaven can not exist,
(314) 530-1981                          If the family is not eternal"
bpm@techapp.com                   F. Ballard Washburn
Received on Wednesday, 19 February 1997 19:03:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 9 April 2012 12:13:26 GMT