W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2010

ISSUE-114 (CORS-credentials): CORS does not define the effect of the credentials flag in sufficient detail [CORS]

From: Web Applications Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Wed, 3 Feb 2010 09:19:30 +0000 (GMT)
To: public-webapps@w3.org
Message-Id: <20100203091930.A02BE7F408@otto.w3.org>

ISSUE-114 (CORS-credentials): CORS does not define the effect of the credentials flag in sufficient detail [CORS]

http://www.w3.org/2008/webapps/track/issues/114

Raised by: Maciej Stachowiak
On product: CORS

It looks like the only actual statement about the effect of the credentials flag is:

"Whenever the make a request steps are applied, make a request to request URL, using method request method, entity body request entity body, including the custom request headers, and include credentials if the credentials flag is true (e.g. HTTP authentication data and cookies)."

There's two problems with this:

(1) It's not normatively defined what constitutes a credential.
(2) It says to include credentials when the credentials flag is true, but it doesn't say they must not be included when the credentials flag is false.

I think the credentials flag should specifically affect cookies, http authentication, and client-side SSL certs, but not proxy authentication (or, obviously, Origin). 
Received on Wednesday, 3 February 2010 09:19:32 GMT

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