GNOME Bugzilla – Bug 89583
view source requests don't send cookies (was bug #89554)
Last modified: 2004-12-22 21:47:04 UTC
I understand this might be a Mozilla problem, but I'm not sure. Using view-source:<url> doesn't send any cookie information. Here's something to try if you've got an Amazon.com account... 1. Using Galeon, go to http://amazon.com/ and make sure you are recognized (you should see a message under the nav bar that says something to the effect of, "Hello, YOURNAME. Blah blah blah. (If you're not YOURNAME, click here.)"; if it doesn't, then log in). 2. Type 'view-source:' in front of the Amazon.com URL and hit return. 3. Hit C-f or select Edit -> Find... and do a search for YOURNAME in the source. You won't find it. You'll get something like: <font face=verdana,arial,helvetica size=-1><font color=#CC6600><b>Hello.</b></font> Sign in to get <a href=...>personalized recommendations</a>. New customer? <a href=...>Start here</a>. </font> Amazon.com stores a key to their user information in the ubid-main or xmain cookies (I think). Since these don't get sent during the retransmission of the source, then the app will behave differently. Cached or uncached, 1.2.5 doesn't send the cookies with the request when displaying the source. $ rpm -qa | grep '(mozilla|galeon)' | sort galeon-1.2.5-2.ximian.3 mozilla-1.0.0-5.ximian.1 mozilla-chat-1.0.0-5.ximian.1 mozilla-dom-inspector-1.0.0-5.ximian.1 mozilla-js-debugger-1.0.0-5.ximian.1 mozilla-mail-1.0.0-5.ximian.1 mozilla-nspr-1.0.0-5.ximian.1 mozilla-nss-1.0.0-5.ximian.1 mozilla-psm-1.0.0-5.ximian.1 nautilus-mozilla-1.0.6-15.ximian.14
Cookies are neither here or there. When it displays the cached copy of a page in view-source no interaction with the server is undertaken. I cannot reproduce your problem. I suggest you try again with a on-zero disk cache. It is possible that the mozilla code always pulls the ached copy from the disk cache. If this is a case, then it's a mozilla bug and should be filed with them, though I'm 99% sure that a bug will already exist if it is the case. As stated before prepending view-source: is the non-cached view source and the stateless behaviour your observe is exactly what is to be expected.
Okay, this is really frustrating. I will make this as clear as I can: THIS BUG HAS NOTHING TO DO WITH CACHING. 1. Open a browser. 2. Type in view-source:<url> 3. Observe that cookies are not sent with the request Here is the request to http://nautilusnetwerks.com/: GET / HTTP/1.1 Host: nautilusnetwerks.com User-Agent: Mozilla/5.0 Galeon/1.2.5 (X11; Linux i686; U;) Gecko/20020606 Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,text/css,*/*;q=0.1 Accept-Language: en Accept-Encoding: gzip, deflate, compress;q=0.9 Accept-Charset: ISO-8859-1, utf-8;q=0.66, *;q=0.66 Keep-Alive: 300 Connection: keep-alive Referer: http://bogosian.net/ Cookie: xoops_session=34170cffea1e8c7c8d5a5726d20885b0 Here is the request to view-source:http://nautilusnetwerk.com/: GET / HTTP/1.1 Host: nautilusnetwerks.com User-Agent: Mozilla/5.0 Galeon/1.2.5 (X11; Linux i686; U;) Gecko/20020606 Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,text/css,*/*;q=0.1 Accept-Language: en Accept-Encoding: gzip, deflate, compress;q=0.9 Accept-Charset: ISO-8859-1, utf-8;q=0.66, *;q=0.66 Keep-Alive: 300 Connection: keep-alive Notice that the Cookie: header is missing.