Summary: | Plain Text Representations of XML Source Code without .txt Extension Result in Parsing | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Hugh Guiney <hugh> | ||||
Component: | Page Loading | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | UNCONFIRMED --- | ||||||
Severity: | Normal | CC: | abarth, ahmad.saleem792, annevk, ap | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | Mac | ||||||
OS: | OS X 10.5 | ||||||
Attachments: |
|
Description
Hugh Guiney
2010-10-19 23:11:33 PDT
The draft specification governing content type sniffing is at <http://tools.ietf.org/html/draft-abarth-mime-sniff>. I don't know whether Safari works in accordance with it here. The draft prevent sniffing of XML from text/plain. Safari does sniff from text/plain in some cases. The same document may still get sniffed as HTML. I guess we need to have the original document to find out what exactly happened. Reporter, would it be possible for you to upload it? Created attachment 71322 [details]
XHTML as Plain Text
Thanks! Yes, that's sniffed as <application/xhtml+xml>. Adam, what does the spec say? Should it be text/plain, or text/html? > Adam, what does the spec say? Should it be text/plain, or text/html?
text/plain. We should never sniff HTML or XML from text/plain. The spec says text/plain can only become types that are not scriptable.
|