Log information for diagnosing NS_ERROR_CORRUPTED_CONTENT errors into web console

NEW
Unassigned

Status

()

P3
normal
7 years ago
a year ago

People

(Reporter: briansmith, Unassigned)

Tracking

({dev-doc-needed})

Trunk
All
Mac OS X
dev-doc-needed
Points:
---

Firefox Tracking Flags

(firefox6 unaffected, firefox7+ affected, firefox8 affected)

Details

(Whiteboard: [necko-backlog], URL)

+++ This bug was initially created as a clone of Bug #681140 +++

When we emit a NS_ERROR_CORRUPTED_CONTENT error, we should emit the multiple values of the header(s) that we are causing the problem to the web console. Then, we should update the MDN and/or SUMO article for NS_ERROR_CORRUPTED_CONTENT so that it explains how to use diagnose this problem using the web console.

I think we can do this faster than we can implement the (good) suggestion in bug 669259.
Removing critical designation based on guidelines here https://bugzilla.mozilla.org/page.cgi?id=fields.html#severity
Severity: critical → normal
Why do you don't add a useful text in the error message like for example the technical details in ssl error pages ?
I bet that most users and server admins don't look in the error Console.
We should also log into the NSPR log.

Comment 5

7 years ago
If the content is corrupted due to invalid HTTP headers returned, the Web console does not show any response from the server. See bug 690202.

Comment 6

7 years ago
As a user of firefox who got bitten by this problem,
I second the idea of 

 - the original post about putting some 
   easy to notice, very visible page about the issues, 

 - comment 2 (nice albeit it may take some time considering the I18N issues),

 - and comment 4 (important for diagnosing future similar issues.)

 
It took me a while to figure out the problem (about one full evening) after an intranet page served by "Trac" add-on to auto download PDF file caused the
said error. In this case it was two inconsistent content-disposition: headers (first inline, then attachment.).

I am surprised that mozilla newsgroups are not full of the issues related with this one. But at least, if you search for google, there are people who are bitten by this problem in the last several days with no clues at all initially including myself.

A clear page that explains the issue and can be searched by google will be appreciated very much!

Comment 7

7 years ago
in bug 690202 comment 2 I had a link to a test case that I made. It would be great if devs or even users could get some more useful information out of this error. 

It says "Please contact the website owners to inform them of this problem." but if you are the owner there is no way to figure it out since FF7+ is the only browser I have ran into that has this error.

My examples are on http://test.scotepi.net/ff690202/
Whiteboard: [necko-backlog]
You need to log in before you can comment on or make changes to this bug.