Open Bug 541818 Opened 15 years ago Updated 2 years ago

Saving image re-issues request so fails due to hotlink protection

Categories

(Firefox :: File Handling, defect)

x86_64
Linux
defect

Tracking

()

UNCONFIRMED

People

(Reporter: richard.simkins, Unassigned)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2pre) Gecko/20100121 Ubuntu/9.04 (jaunty) Namoroka/3.6pre
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2pre) Gecko/20100121 Ubuntu/9.04 (jaunty) Namoroka/3.6pre

On pages with hotlink protection on images.

If I view an image in the context of the page and then right click -> "Save Image As..." the image will apparently save but will instead save the hotlink placeholder image or other hotlink placeholder content.

Reproducible: Sometimes

Steps to Reproduce:
1.Find a website with hotlink protection of images.
2.View it is the context of the page or on its own with "View Image"
3.Attempt to save it.
Actual Results:  
While attempting to save images in the context of their pages, the request is apparently re-issued. So that for images that are protected from hotlinking, instead of the image stored on my local machine I get the hotlink placeholder image or other hotlink placeholder content.

Expected Results:  
Images should be saved from where they are stored on the local machine (which they always will be because otherwise I wouldn't be able to see it in my browser). The request for the image should not be re-issued because a) It is a waste of bandwidth, and b) images protected from hotlinking will never save.

If I attempt to save an image I want to save the image I see in the page as it is presented on my local machine. I do not want to save the response from a re-issued request (which could be anything).

Re-issuing a request for an image should always be done explicitly by the user.
This is a problem for much more than just the "hotlink".

Redownloading every image that you save by dragging is a real hassle.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.