Closed
Bug 280525
Opened 20 years ago
Closed 9 years ago
Allow "send referrer on images" to be enabled seperately from "send on link"
Categories
(Core :: Networking, enhancement)
Core
Networking
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: david.hagood, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a5) Gecko/20041121 MultiZilla/1.8.0.0a Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a5) Gecko/20041121 MultiZilla/1.8.0.0a Many web sites use the Referer: field to prevent "leeching" their images - they only serve the image when the Referer: header points back to the appropriate page. It would be nice to be able to enable sending them the referrer header for the images, without enabling sending the Referer for link clicks. With the Multizilla pref bar you can select: Don't send referrer Send referrer on link clicks Send referrer on link clicks and images. According to the Multizilla team, the ability to add "Send referrer on images only" is not available from the Mozilla backend. Ideally, I'd want support for referrer to be under control of an ACL, like many of the other systems - a list of sites and their allowed settings, plus an overall policy setting (whitelist/blacklist). Reproducible: Always Steps to Reproduce: 1. Try to set "Send referrer on images only" 2. ??? 3. No Profit (ugly!) Actual Results: There is no ability to do so. Expected Results: Allow me to say "Send referrer on images only"
Assignee: prefs → darin
Component: Preferences → Networking: HTTP
OS: Linux → All
Product: Mozilla Application Suite → Core
QA Contact: networking.http
Hardware: PC → All
Comment 1•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
| Reporter | ||
Comment 2•19 years ago
|
||
This problem still exists.
Comment 3•19 years ago
|
||
-> default owner
Assignee: darin → nobody
Component: Networking: HTTP → Networking
QA Contact: networking.http → networking
Comment 4•9 years ago
|
||
meta referrer, etc..
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•