Improve handling of responses with incorrect content type

NEW
Unassigned

Status

defect
P3
normal
3 years ago
7 months ago

People

(Reporter: sebo, Unassigned)

Tracking

(Blocks 1 bug)

Trunk
Dependency tree / graph

Firefox Tracking Flags

(firefox50 affected)

Details

()

Reporter

Description

3 years ago
Responses served with an incorrect content type are handled correctly by the browser (e.g. CSS and JavaScript are parsed), though are put into the wrong category in the Net Monitor.

This came up recently in the Firebug discussion group:
https://groups.google.com/d/topic/firebug/ZSJmVhEP2-A/discussion

Example:
1. Go to http://www.leihinstrumente.de/
2. Open the Net Monitor
3. Reload the page
4. Switch to the 'Other' filter

=> Several JavaScript files are listed there, because they have 'text/plain' as MIME type.

Firebug does a better job here and lists them under its 'JavaScript' tab.

Sebastian
Reporter

Comment 1

3 years ago
There may be some indication added that the responses have an incorrect content type, e.g. an exclamation mark besides the 'Content-Type' header.

Sebastian

Comment 2

2 years ago
The example at http://www.leihinstrumente.de/ doesn't show this behavior any more since the page moved to a different server, which apparently does it right...

Updated

Last year
Product: Firefox → DevTools
Inactive report, moving to the backlog (P3)

@Sebastian: is this still an issue? Do you have another test case?

Honza
Flags: needinfo?(sebastianzartner)
Priority: P2 → P3
Reporter

Comment 4

7 months ago
I wanted to create a new test case for this at http://zartner.bplaced.net/test/bug1280024.html. Unfortunately, scripts served with a different MIME type are obviously blocked now in live environments (see also bug 1510241). On localhost it can still be reproduced, though.

Sebastian
Flags: needinfo?(sebastianzartner)
You need to log in before you can comment on or make changes to this bug.