Closed
Bug 127935
Opened 24 years ago
Closed 10 years ago
Debug - Networking should have static referrer support
Categories
(Core :: Networking: HTTP, enhancement, P5)
Core
Networking: HTTP
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: pathos, Unassigned)
References
Details
It would be very useful to be able to specify a static referrer (HTTP referer
header value). It would also be useful to specify that the referer may never be
sent with the request.
| Reporter | ||
Updated•24 years ago
|
Depends on: 55477
Summary: Debug - Networking should referrer support → Debug - Networking should have static referrer support
Comment 1•24 years ago
|
||
To HTTP networking
Assignee: sgehani → darin
Status: UNCONFIRMED → NEW
Component: Preferences → Networking: HTTP
Ever confirmed: true
OS: Windows 2000 → All
QA Contact: sairuh → tever
Hardware: PC → All
Updated•24 years ago
|
Status: NEW → ASSIGNED
Priority: -- → P5
Target Milestone: --- → Future
Comment 2•24 years ago
|
||
you can disable the Referer header by setting the following pref:
user_pref("network.http.sendRefererHeader", 0);
-> future
| Reporter | ||
Comment 3•24 years ago
|
||
Not disable (this is bug 55477), but setting it to a static content (for example
a URI). This is useful for debugging and testing web applications. I do not know
a browser who has this feature, and it would be really handy to have.
Comment 4•24 years ago
|
||
I was responding to this part of the bug report:
> It would also be useful to specify that the referer may never be
> sent with the request.
Adding support for a static referrer isn't going to happen anytime soon :(
Comment 5•24 years ago
|
||
> Adding support for a static referrer isn't going to happen anytime soon :(
Is based on technical or political reasons?
It would take ~10 minutes to add this functionality to my patch in bug #55477,
but I really can't see how providing the means to send a static referrer would
be useful to more than a handful of people. Maybe this would be better done by
using an external proxy?
Comment 6•24 years ago
|
||
this bug was futured because it was not deemed critical for mozilla 1.0 ...
sorry, i should have mentioned that.
Comment 7•22 years ago
|
||
A workaround for this bug could be refspoof from mozdev.org
http://refspoof.mozdev.org/
Updated•20 years ago
|
Assignee: darin → nobody
Status: ASSIGNED → NEW
QA Contact: tever → networking.http
Target Milestone: Future → ---
Comment 8•10 years ago
|
||
addon territory
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•