Closed
Bug 571161
Opened 14 years ago
Closed 9 years ago
Eliminate originalURI arg from PHttpChannel::AsyncOpen?
Categories
(Core :: Networking: HTTP, enhancement)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: jduell.mcbugs, Unassigned)
References
Details
It's unclear if any HTTP channel clients ever set originalURI != uri (about:credits?); it's also not clear if chrome channel would ever need to know. So we may be able to eliminate the argument.
Comment 1•14 years ago
|
||
> It's unclear if any HTTP channel clients ever set originalURI != uri
Some extensions sure do. But those would be in the chrome.
HTTP redirects do, but those happen in chrome too, right?
.url/.desktop files pointing to http:// URIs do, I would think. Where do those happen?
Comment 2•9 years ago
|
||
in general, as much should work in the child as possible. if we've got a profile that says this moves the needle, then reassess.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•