Closed Bug 77065 Opened 24 years ago Closed 23 years ago

File: Open Web Location No "file not found" for local file URLs

Categories

(Core :: Networking: File, defect)

x86
Windows 2000
defect
Not set
minor

Tracking

()

VERIFIED DUPLICATE of bug 63048

People

(Reporter: gekacheka, Assigned: dougt)

References

()

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; 0.8.1) Gecko/20010323 BuildID: 2001032319 When a local file URL is followed but not found, Mozilla mysteriously does nothing. Other browsers put up a "file not found" confirmation dialog. Reproducible: Always Steps to Reproduce: 1. File | Open Web Location 2. file://c:/nonexistent.html (or appropriate path for your platform) Actual Results: The dialog goes away and nothing else happens. Expected Results: Some indication that the file was not found. Both IE5 and NN4.7 pop up an error dialog when a local file URL is not found. (Maybe Mozilla is expecting the server to return an error page, but there is none... :) I originally ran into the problem from a bookmark to a local file which no longer existed, so it is not only a problem with the dialog. The "file not found" message should apply whenever a local file URL is opened.
dup of bug 76434 "local file needs to give error message when file not found"
*** This bug has been marked as a duplicate of 19073 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Summary: No "file not found" for local file URLs → File: Open Web Location No "file not found" for local file URLs
QA Contact: tever → benc
REOPEN: really a dupe of bug 63048 (b/c I it is fixed in Mozilla 0.9.5 per dougt's comments about trunk fixing after 0.9.4 branch).
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
*** This bug has been marked as a duplicate of 63048 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago23 years ago
Keywords: verifyme
Resolution: --- → DUPLICATE
VERIFIED: file: URL cleanup.
Status: RESOLVED → VERIFIED
Keywords: verifyme
You need to log in before you can comment on or make changes to this bug.