W3C home > Mailing lists > Public > public-webapi@w3.org > June 2007

Re: Recent spec change to XMLHttpRequest default Content-Type

From: Jim Ley <jim@jibbering.com>
Date: Fri, 15 Jun 2007 09:10:39 +0100
Message-ID: <0d2d01c7af24$a9a89670$0301a8c0@Sniff>
To: "Julian Reschke" <julian.reschke@gmx.de>, "Carsten Orthbandt" <carsten@pixeltamer.net>
Cc: "Web API WG \(public\)" <public-webapi@w3.org>

"Julian Reschke" <julian.reschke@gmx.de>
> I have to agree here. If a recipient decides to do content-type guessing, 
> the fact that the type is not what was tested is not an error. One more 
> reason not to guess in the first place.

But it might be what's tested just invalid - if the user expected the 
sniffing behaviour he'd then be wondering why it wasn't getting a document, 
or any errors, in situations that rely on guesswork of content, it should be 
left to the browser what that guesswork is.

> However, IMHO the right thing to do here is to attach a proper 
> content-type header in the first place.

Yes, it's not an error that developers should ever be seeing, just ensure 
there's a content type appropriate to the content, so I think it's a pretty 
artificial problem.

Received on Friday, 15 June 2007 08:10:55 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:23 UTC