W3C home > Mailing lists > Public > public-webapi@w3.org > May 2008

XHR vs setting request headers

From: Julian Reschke <julian.reschke@gmx.de>
Date: Fri, 16 May 2008 12:15:33 +0200
Message-ID: <482D5EC5.6090206@gmx.de>
To: "Web API WG (public)" <public-webapi@w3.org>


inspired by Laurens' experiment with Accept I just did some tests with 

When setting Content-Type twice, IE7 behaves as specified (sending a 
*broken* Content-Type header), while Firefox3 simply sends the second 
value that was set.

So apparently, the two most widely used browsers differ in what they do.

Is it really a good idea to standardize on what IE does, *knowing* that 
it may cause broken requests to be generated?

BR, Julian

PS: it's a bit ironic if the same group of people standardizes APIs that 
make it dead easy to generate invalid headers then complains to the HTTP 
WG for the lack of defined behaviour for broken requests...
Received on Friday, 16 May 2008 10:16:19 UTC

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