On 29 Feb 2008, at 16:33, Julian Reschke wrote:
Geoffrey Sneddon wrote:
It seems like the HTTP spec should define how to handle that, but
the HTTP working group has indicated a desire to not specify
error handling behaviour, so I guess it's up to us.
IE and Safari use the first one,
Geoffrey Sneddon wrote:
Content-Type: XML
Content-Type: text/XML
Using the first would break badly. I guess it seems to work because of
content-type sniffing on an unknown (and invalid) header
Or because the header parser uses the first header that actually looks like a
valid content-type
