Save Page As.. for some secure pages results in file that won't open




File Handling
10 years ago
8 years ago


(Reporter: Erik Harris, Unassigned)


Firefox Tracking Flags

(Not tracked)


(Whiteboard: [CLOSEME 2010-11-15], URL)



10 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/2008070208 Firefox/3.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/2008070208 Firefox/3.0.1

Some secure pages have code in them that changes the URL in a manner that causes a saved page to be unopenable.  Somewhat recently, NewEgg added the following JavaScript code to the headers of their secure pages (including receipts, which I prefer to save, instead of print):


This causes saved purchase receipts to redirect from "file:///C:/..." to "https://c/...", giving an error that no server exists at "c".

Some other sites use various different methods that break Firefox's Sage Page As... feature

Reproducible: Always

Steps to Reproduce:
1. Buy something at NewEgg
2. Save the receipt
3. Try opening the receipt
Actual Results:  
File fails to open because Firefox looks for an HTTPS server in the location of the file

Expected Results:  
Firefox already edits an HTML file upon save to replace image locations with the files saved on the hard drive.  The Save As parser should be modified to look for redirects that will "break" the saved file.  One example is given above, using a JavaScript URL rewrite command.

I've seen other secure sites exhibit similar behavior, but I've also successfully saved many secure pages.  There is no easy workaround to this problem - the user must know enough HTML, JavaScript, etc, to be able to edit the saved HTML file, troubleshoot the cause of the problem, and manually edit the saved file appropriately.
This bug was reported using Firefox 3.0 or older, which is no longer supported. The bug has also not been changed in over 500 days and is still in UNCO.
Reporter, please retest this bug in Firefox 3.6.10 or later using a fresh profile, If you still see this problem, please update the bug. If you no longer see the bug, please set the resolution to RESOLVED, WORKSFORME.

This is a mass search of unconfirmed bugs that have no activity on them, so if you feel a bug was marked in error, just remove the CLOSEME comment in the whiteboard within the next month.
Whiteboard: [CLOSEME 2010-11-15]
No reply, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile ( If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.