Open Bug 364354 Opened 18 years ago Updated 2 years ago

Content-Disposition attachment vs 4xx status code from server

Categories

(Firefox :: File Handling, defect)

x86_64
Windows 7
defect

Tracking

()

People

(Reporter: julian.reschke, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0

When a Content-Disposition response header of type "attachment" is sent back with a non-2xx status code (such as 403), Firefox behaves as if everything is ok, potentially tricking the user to believe that the page (s)he wanted to save was actually saved.

Allowing to continue saving probably is good, but there really should be a warning displayed that the content is unlikely to be the one the user expects.

Reproducible: Always
Component: General → File Handling
QA Contact: general → file.handling
Reporter, do you still see this problem with the latest Firefox 2? If not, can you please close this bug as WORKSFORME. Thanks!
Whiteboard: CLOSEME 07/14
Version: unspecified → 2.0 Branch
Informing the user of the error seems reasonable in this case.
Whiteboard: CLOSEME 07/14
This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME
http://www.mozilla.com
http://support.mozilla.com/kb/Managing+profiles
http://support.mozilla.com/kb/Safe+mode
I have added a test case at:

  http://greenbytes.de/tech/tc2231/#attonly403

Firefox now displays an error message, which is good. The actual text "file not found" though is sub-optimal.
Version: 2.0 Branch → 3.6 Branch
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → Windows 7
Hardware: x86 → x86_64
Version: 3.6 Branch → Trunk
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.