The type of data of responses should only be identified by the Content-Type value that was sent. It should not be tried to "guess" the content type. Examples: * If a HTML document contains a link to an external CSS stylesheet only responses with the Content-Type value "text/css" should be accepted. * If a HTML document embedds an image via the IMG element only responses with valid values for image types (e.g. "image/...") should be accepted.
Markus, could you provide test cases or real examples of buggy, according you, behavior of WebKit? You should notice, that HTML5 specification defines content sniffing as other *proper* method of determining resource content type: http://www.whatwg.org/specs/web-apps/current-work/#content-type-sniffing
Created attachment 22551 [details] Using as self-reference as external stylesheet At least the latest Safari version (5525.20.1) accepts a document sent as text/html to be used as an external stylesheet.
(In reply to comment #2) > Created an attachment (id=22551) [edit] > Using as self-reference as external stylesheet > > At least the latest Safari version (5525.20.1) accepts a document sent as > text/html to be used as an external stylesheet. > (In reply to comment #2) > Created an attachment (id=22551) [edit] > Using as self-reference as external stylesheet > > At least the latest Safari version (5525.20.1) accepts a document sent as > text/html to be used as an external stylesheet. > This bug was fixed long time ago. Check bug 17298 for details. What about the other case: "If a HTML document embedds an image via the IMG element only responses with valid values for image types (e.g. "image/...") should be accepted."? Do you have test case for it?
No, I have no test case.
(In reply to comment #4) > No, I have no test case. > So I assume that I can close the bug report. Markus, feel free to reopen this report if you have real example of reported image issue.