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

Re: Recent spec change to XMLHttpRequest default Content-Type

From: Anne van Kesteren <annevk@opera.com>
Date: Fri, 15 Jun 2007 12:20:39 +0200
To: "Carsten Orthbandt" <carsten@pixeltamer.net>
Cc: "Web API WG (public)" <public-webapi@w3.org>
Message-ID: <op.ttykcpc964w2qv@annevk-t60.oslo.opera.com>

On Fri, 15 Jun 2007 12:08:06 +0200, Carsten Orthbandt  
<carsten@pixeltamer.net> wrote:
> If the spec clearly said "if there is no Content-Type specified, the
> UA should try to treat it as XML, but not raise any error conditions
> if parsing fails" there would be no compatibility issues and the
> behaviour of (compliant) XHR implementations would actually match
> the rules set out in the HTTP protocol.
> If it is actually intended to raise XML errors on untyped content
> this would IMHO be a important difference to the HTTP RFC.

The specification once had a concept of what is and what is not conforming  
for scripts to do, but it was to much of a hassle so that has been  
dropped. Whether or not user agents show an error message is up to them  

Anne van Kesteren
Received on Friday, 15 June 2007 10:20:45 UTC

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