W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2011

[cors] The case of Http Headers in Access-Control-Request-Headers

From: Benson Margulies <bimargulies@gmail.com>
Date: Wed, 21 Dec 2011 21:43:08 -0500
Message-ID: <CALhtWkehLw50_2sti5AGxLoPgdreXc4Adm-FS0f+7zK6GkK7wA@mail.gmail.com>
To: public-webapps@w3.org

I just made a small discovery;

Chrome 16 sends, e.g.

  Access-Control-Request-Headers: Content-Type

Firefox 8.0 sends, contrastively:

  Access-Control-Request-Headers: content-type

Given the requirement for case-sensitive comparison in the spec, this
to me suggests that one of them is wrong. Which?

Received on Thursday, 22 December 2011 02:43:44 GMT

This message: [ Message body ]
Next message: Boris Zbarsky: "Re: [cors] The case of Http Headers in Access-Control-Request-Headers"
Previous message: Benson Margulies: "[cors] Should browsers send non-user-controllable headers in Access-Control-Request-Headers?"
Next in thread: Boris Zbarsky: "Re: [cors] The case of Http Headers in Access-Control-Request-Headers"
Reply: Boris Zbarsky: "Re: [cors] The case of Http Headers in Access-Control-Request-Headers"

Mail actions: [ respond to this message ] [ mail a new topic ]
Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]
Help: [ How to use the archives ] [ Search in the archives ]

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:49 GMT