Bug 54463

Summary: Invalid text/html mime type reported for a 304 Not Modified image/unknown resource
Product: WebKit Reporter: Terry Riegel <riegel>
Component: WebKit Misc.Assignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: apavlov, bweinstein, joepeck, keishi, loislo, pfeldman, pmuellr, riegel, rik, timothy, yurys
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
URL: http://positiveaction.org/newsite/productimages/senn610THUMB

Terry Riegel
Reported 2011-02-15 08:14:49 PST
I have a URI... http://positiveaction.org/newsite/productimages/senn610THUMB This is a jpeg image. Apache is sending it as Content-Type : image/jpeg and Safari recieves it as such. I have verified this with the Charles web debugging proxy. On a page that includes this image via <img src="http://positiveaction.org/newsite/productimages/senn610THUMB"> I hit refresh, and the web server responds with 304 Not Modified. This is as it should be. However, when this happens web inspector sends this warning message... Resource interpreted as image but transferred with MIME type text/html Thanks, Terry Riegel
Attachments
Alexander Pavlov (apavlov)
Comment 1 2011-02-28 09:56:05 PST
Here are the headers I received with curl -D headers.log http://positiveaction.org/newsite/productimages/senn610THUMB HTTP/1.1 200 OK Date: Mon, 28 Feb 2011 17:41:56 GMT Server: Apache/2.2.9 (Fedora) Last-Modified: Tue, 15 Feb 2011 18:34:53 GMT ETag: "1548265-424-49c566b96ad40" Accept-Ranges: bytes Content-Length: 1060 Connection: close Content-Type: image/unknown So, it is not image/jpeg but image/unknown. On a refresh, the resource does receive the "text/html" mime type, which is presumably due to the Safari network stack, tested on Windows 7 (Chrome reports the same "image/unknown" mime type for this 304 Not Modified). This is not a Web Inspector issue per se, so I'm changing the title and component appropriately.
Alexander Pavlov (apavlov)
Comment 2 2011-04-04 04:48:06 PDT
Got fixed as a side effect of the bug 48525 fix.
Note You need to log in before you can comment on or make changes to this bug.