198455 - cookies being set by server (response.cookies) are set in Cookie Manager but not available in document.cookie

Status: RESOLVED EXPIRED

(Core :: Networking: Cookies, defect)

Description

[Thad Hoffman]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.3) Gecko/20030312

An ASP page is setting Response.cookies("value") and Moz is registering it in
the cookie manager but it does not show up at all in document.cookies.

This happens in all builds Mac OS X and Win23 from 1.0.1 - 1.3 release.

To test use an ASP page that sets Response.Cookies() and alert document.cookie
in Moz or use Venkman to inspect the cookie.

Reproducible: Always

Steps to Reproduce:
1. log onto  a page that sets a cookie in an ASP page (Response.Cookies("test")
= "hello")
2. on the client either alert the document.cookies or use venkman to break and
inspect the cookie
3. open cookie manager and locate the cookie set by the ASP page

Actual Results:  
Cookie is set and shows in the cookie manager, not available or visible in
document.cookie

Expected Results:  
put the cookie in the document.cookie property

Cookies set in client function fine, they show up in both document.cookie and
the cookie manager

Comment 1

[Thad Hoffman]

Attachment: screen shot of the cookie manager after setting cookies via ASP

Here is what the document.cookie has in it:
DorUser=kinch; Company=COR236; Group=cfull;
ASPSESSIONIDGGGGGMWC=BHONKJFANEBGALDLKFOEHJHD; GFXSITENAME=fw_chase_portal;
NOXYTHEME=skins/vporter

Notice the "HeyThad" and the "GFXSessionID" cookies (both set in the ASP file)
are not present above but show up in the cookie manager gif.

Strange thing is that the ASPID that is set automatically by ASP shows up in
both places.

Comment 2

[Owen Marshall (Not reading bugmail)]

cc dwitte regarding cookie issues. dwitte, you did work on this, yes...?

Comment 3

[Boris Zbarsky [:bzbarsky]]

what is the header that sets the cookies?

Comment 4

[Thad Hoffman]

I don't have a way/ know of a way to see the http headers. 

When debugging the ASP, I can see the the request is coming in with the cookies
set previously by ASP, but I can't get to them via the document still...

Here is what the ASP is doing (if it helps):

Response.Cookies("HeyThad") = "Yo!"
corrName=corrNode.text		
Response.Cookies("GFXSessionID") = strSessionID
strURL = "GFXSite.htm?corr=" & corrName
Response.Redirect(strURL)

Here is the debugger watch info for the response and request objects:
- Response              Object
-	Cookies		Object
 	Item		Variant
 	_NewEnum		Object
 	Count	2	Integer
 	Key		Variant
 	Status	"200 OK"	String
 	CharSet	""	String
 	CacheControl	"private"	String
 

-	request		Object
 	Item		Object
+	QueryString		Object
+	Form		Object
+	Body		Object
+	ServerVariables		Object
+	ClientCertificate		Object
-	Cookies		Object
 	Item
"GFXSessionID=%7B3E7A23B2451B2EC25C7C385B3E31D8B0221E%7D%40thoffman%2Dw2k;HeyThad=Yo%21;group=cfull;company=COR236;dorUser=user"
Variant
 	_NewEnum		Object
 	Count	2	Integer
 	Key		Variant
 	TotalBytes	0	Long

Comment 5

[Christian :Biesinger (don't email me, ping me on IRC)]

see http://livehttpheaders.mozdev.org/ for a way to see http headers...

Comment 6

[Thad Hoffman]

Attachment: attached the headers captured in Moz

Thanks for that link. Cool tool, wishing for an OS X port :-) ....

Comment 7

[Johnny Stenback (:jst)]

Over to Cookies.

Comment 8

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 9

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.