firefox does not show 404 error on dead link

Bug #259783 reported by David Balažic on 2008-08-20
4
Affects Status Importance Assigned to Milestone
Mozilla Firefox
Invalid
Medium
firefox-3.0 (Ubuntu)
Low
Unassigned

Bug Description

Using Firefox on Ubuntu 8.04.1 amd64
I visited http://zerowing.idsoftware.com/linux/etqw/

Under 2.1 Retail Game I clicked the first link (for ETQW-client-1.4-full.x86.run) I get ... nothing.

No download. No Error report. Nothing.

using wget on same URL gives a 404 error.

So it is a dead link, but firefox stays ... "dumb".

Firefox is 3.0.1
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.1) Gecko/2008072820 Firefox/3.0.1

The server sends zero content for the 404-
Shouldn't we display an internal error page if the server responds with an empty response for a 404 ?

HTTP Status Code: HTTP/1.1 404 Not Found
Connection: close
Date: Fri, 27 Jun 2008 16:42:57 GMT
Server: Microsoft-IIS/6.0
IISExport: This web site was exported using IIS Export v4.1
X-Powered-By: ASP.NET
Content-Length: 0
Content-Type: text/html
Expires: Fri, 27 Jun 2008 16:41:57 GMT
Set-Cookie: ASPSESSIONIDQSBDBQQD=LMLNDEICAKLAFGEMNJACLKND; path=/
Cache-control: private

David Balažic (xerces8) wrote :

Using Firefox on Ubuntu 8.04.1 amd64
I visited http://zerowing.idsoftware.com/linux/etqw/

Under 2.1 Retail Game I clicked the first link (for ETQW-client-1.4-full.x86.run) I get ... nothing.

No download. No Error report. Nothing.

using wget on same URL gives a 404 error.

So it is a dead link, but firefox stays ... "dumb".

Firefox is 3.0.1
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.1) Gecko/2008072820 Firefox/3.0.1

Andreas Moog (ampelbein) wrote :

Confirmed on Intrepid. Attached is Livehttp-logfile, the response is correct, just gets not correctly interpreted.

Andreas Moog (ampelbein) wrote :
Andreas Moog (ampelbein) wrote :

I reported the bug Upstream, you can track it here:
https://bugzilla.mozilla.org/show_bug.cgi?id=452222

Changed in firefox:
status: Unknown → New
Changed in firefox:
status: New → Confirmed

*** Bug 452222 has been marked as a duplicate of this bug. ***

*** Bug 454006 has been marked as a duplicate of this bug. ***

Andreas Moog (ampelbein) on 2008-09-06
Changed in firefox:
status: Confirmed → Unknown
Changed in firefox-3.0:
importance: Undecided → Low
status: Confirmed → Triaged
Changed in firefox:
status: Unknown → Confirmed

*** Bug 466791 has been marked as a duplicate of this bug. ***

Changed in firefox:
importance: Unknown → Medium

Created attachment 480930
Patch to show internal error pages for HTTP error in the 400/500 range

Based on Curtis' patch in bug 482874 I created a similar patch to show error pages for all types of HTTP errors.

I left in the possibility to configure the maximum amount of server-side message length to trigger the override, though the default is 0.

I removed all references to 404.

The texts could surely stand some improvement, I basically copied the first sentences from RFC 2616.

When the patch for bug 482874 is landed, this one could be updated to use the same code then.

Comment on attachment 480930
Patch to show internal error pages for HTTP error in the 400/500 range

Asking ehsan for review, as he also looked into the original patch at bug 482874.

Comment on attachment 480930
Patch to show internal error pages for HTTP error in the 400/500 range

Sorry, I only reviewed that patch for RTL concerns, and I'm not the best person to review this one. I'll forward your request to Boris and Axel tentatively.

Why don't we just land the patch from bug 482874 instead of duplicating parts of it?

Comment on attachment 480930
Patch to show internal error pages for HTTP error in the 400/500 range

Per comment 8....

*** Bug 876682 has been marked as a duplicate of this bug. ***

There is a patch from 2011, so it wasn't applied to release versions?

As far as I know Firefox is the only browser that simply displays a blank page instead of relaying HTTP error messages to the user.

It wasn't applied, correct. It failed to pass the code review process...

If you're interested in this, I suggest driving bug 482874 in.

Changed in firefox:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.