Closed
Bug 47353
Opened 24 years ago
Closed 23 years ago
ModifyRequest HTTPNotify listener is called before all headers are set
Categories
(Core :: Networking: HTTP, defect, P3)
Tracking
()
VERIFIED
FIXED
mozilla1.0
People
(Reporter: toml, Assigned: darin.moz)
References
Details
From Bugzilla Helper: User-Agent: Mozilla/4.72 [en] (WinNT; U) BuildID: 2000073008 The ModifyRequest HTTPNotify listener is called before all headers have been set. I am working on Platform for Privacy Preferences (P3P) which has a concept of a "safe zone." Whenever requesting P3P related files, certain headers should not be sent (cookies, agent and referer). However, I can't remove these headers since they are set after the call to ModifyRequest. Reproducible: Always Steps to Reproduce: 1. Go to any web page Actual Results: When the ModifyRequest HTTPNotify listener is called not all of the headers that will flow on the request have been set. Expected Results: All of the headers that will flow on the request should be set before the invocation of the ModifyRequest HTTPNotify listener. Attached is a diff with a change that I made to nsHTTPChannel.cpp to cause the redrive of the original headers.
Reporter | ||
Comment 1•24 years ago
|
||
Just re-read what I wrote. The last paragraph on the original submission was left over from a previous submission. I don't have any diffs for this problem.
Comment 2•24 years ago
|
||
Confirming for triage. Thomas Lendacky - I have upgraded your Bugzilla priviledges so you create NEW bugs by default, as you are a developer. Gerv
Status: UNCONFIRMED → NEW
Ever confirmed: true
http bugs to "Networking::HTTP"
Assignee: gagan → darin
Component: Networking → Networking: HTTP
Target Milestone: Future → M19
Assignee | ||
Updated•24 years ago
|
Target Milestone: --- → Future
Assignee | ||
Comment 4•24 years ago
|
||
hoping to fix this for moz 1.0
Target Milestone: Future → mozilla1.0
Assignee | ||
Comment 5•23 years ago
|
||
this should be fixed now... reporter: please verify against a recent nightly build. thanks!
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Old stuff. Catching up. If this is still a problem, please reopen. Marking Verified!
Status: RESOLVED → VERIFIED
QA Contact: tever → jimmylee
You need to log in
before you can comment on or make changes to this bug.
Description
•