Closed Bug 155038 Opened 23 years ago Closed 23 years ago

Cookies aren't sent from sidebar when "enable cookies for the originating site only" is set

Categories

(Core :: Networking: Cookies, defect, P2)

x86
Linux
defect

Tracking

()

VERIFIED FIXED
mozilla1.1beta

People

(Reporter: bbaetz, Assigned: morse)

References

()

Details

(Whiteboard: [verified-trunk] [ETA 07/16])

Attachments

(1 file)

Bugzilla now comes with a sidebar. However, cookies aren't being sent to the website, so the result sidebar is as if you wren't logged in. To reproduce: 1) Make sure you're logged into bugzilla 2) Have the cookie pref set to originating site only 3) click the js link in the URL field to install the sidebar. Results: 1) Unlogged in data is shown Expected: 1) Logged in data, including any saved queries, and so on is shown This occurs with 1.0 and CVS from a couple of days ago. Loading sidebar.cgi directly into the browser window produces the expected results. The reason for this is that cookies aren't being sent for loads from the browser. Using printf, it turns out that the cookie module is given a chrome url as the source uri for the load from the sidebar, and the chrome url is considered to be foreign to the http one. I don't know if we should fix cookies to consider chrome urls to be special, or if the sidebar needs to do something.
Status: NEW → ASSIGNED
Priority: -- → P2
Target Milestone: --- → mozilla1.1beta
Summary: Cookies aren't sent from sidebar when "enable cookies for the orignating site only is set" → Cookies aren't sent from sidebar when "enable cookies for the originating site only is set"
Summary: Cookies aren't sent from sidebar when "enable cookies for the originating site only is set" → Cookies aren't sent from sidebar when "enable cookies for the originating site only" is set
Comment on attachment 90592 [details] [diff] [review] never consider chrome URLs to be foreign sr=alecf
Attachment #90592 - Flags: superreview+
Comment on attachment 90592 [details] [diff] [review] never consider chrome URLs to be foreign r=bbaetz. Why doesn't this code use nsIURI, btw?
Attachment #90592 - Flags: review+
Probably because it's legacy code.
Fixed on trunk
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
verified trunk - 07/12/02 builds - winNT4, linux rh6, mac osX needs tested on branch
Status: RESOLVED → VERIFIED
Whiteboard: [verified-trunk]
Actually I wasn't considering nominating this for branch checkin. But since it's such a safe patch, maybe I will.
Keywords: nsbeta1
adt1.0.1+ (on ADT's behalf) approval for checkin to the 1.0 branch, pending Drivers' approval. pls check this in asap, the replace "mozilla1.0.1+" with "fixed1.0.1". thanks!
Blocks: 143047
Whiteboard: [verified-trunk] → [verified-trunk] [ETA 07/16]
Comment on attachment 90592 [details] [diff] [review] never consider chrome URLs to be foreign a=chofmann for 1.0.1
Attachment #90592 - Flags: approval+
Keywords: verified1.0.1
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: