[webappsec + webapps] CORS to PR plans

2013-07-16 Thread Brad Hill
WebAppSec and WebApps WGs, CORS advanced to Candidate Recommendation this January, and I believe it is time we consider advancing it to Proposed Recommendation. In the absence of an editor, I have been collecting bug reports sent to the public-webappsec list, and now have a proposed draft incorp

Re: [webappsec + webapps] CORS to PR plans

2013-07-16 Thread Anne van Kesteren
On Tue, Jul 16, 2013 at 3:47 PM, Brad Hill wrote: > 1. Changed "Fetch" references. The CR document referenced the WHATWG Fetch > spec in a number of places. This was problematic due to the maturity / > stability requirements of the W3C for document advancement, and I feel also > inappropriate, a

Re: [webappsec + webapps] CORS to PR plans

2013-07-18 Thread Arthur Barstow
On 7/16/13 3:47 PM, ext Brad Hill wrote: CORS advanced to Candidate Recommendation this January, and I believe it is time we consider advancing it to Proposed Recommendation. In the absence of an editor, I have been collecting bug reports sent to the public-webappsec list, and now have a propo

Re: [webappsec + webapps] CORS to PR plans

2013-08-05 Thread Brad Hill
I'd like to issue this as a formal Call for Consensus at this point. If you have any objections to CORS advancing to Proposed Recommendation, please reply to public-webapp...@w3.org. Affirmative response are also encouraged, and silence will be taken as assent. The proposed draft is available at

Re: [webappsec + webapps] CORS to PR plans

2013-08-06 Thread Arthur Barstow
On 8/5/13 7:48 PM, ext Brad Hill wrote: I'd like to issue this as a formal Call for Consensus at this point. If you have any objections to CORS advancing to Proposed Recommendation, please reply to public-webapp...@w3.org . Affirmative response are also encour

Re: [webappsec + webapps] CORS to PR plans

2013-08-06 Thread Anne van Kesteren
On Tue, Aug 6, 2013 at 12:48 AM, Brad Hill wrote: > I'd like to issue this as a formal Call for Consensus at this point. If you > have any objections to CORS advancing to Proposed Recommendation, please > reply to public-webapp...@w3.org. Affirmative response are also encouraged, > and silence w

Re: [webappsec + webapps] CORS to PR plans

2013-08-07 Thread Glenn Adams
On Wed, Aug 7, 2013 at 8:54 AM, Glenn Adams wrote: > > On Mon, Aug 5, 2013 at 5:48 PM, Brad Hill wrote: > >> I'd like to issue this as a formal Call for Consensus at this point. If >> you have any objections to CORS advancing to Proposed Recommendation, >> please reply to public-webapp...@w3.or

Re: [webappsec + webapps] CORS to PR plans

2013-08-12 Thread Brad Hill
Anne, Sorry for the delayed reply. If you look at the diff-marked version, you'll see the links to WHATWG Fetch that I updated. As far as the full range of success status codes, if you look at Boris Zbarsky's comments in the thread linked, it seems that Firefox was only planning to implement

Re: [webappsec + webapps] CORS to PR plans

2013-08-12 Thread Brad Hill
OK, tests at: http://webappsec-test.info/~bhill2/CORS/status-async.htm Show that at least Blink and Firefox interop on the full range of 200 status codes, so I'll update the edited PR appropriately and reset the CfC. -Brad On Mon, Aug 12, 2013 at 11:57 AM, Brad Hill wrote: > Anne, > > Sorry

Re: [webappsec + webapps] CORS to PR plans

2013-08-16 Thread Brad Hill
Based on the feedback received during the Call for Consensus, I've updated the draft CORS PR at: http://webappsec-test.info/~bhill2/pub/CORS/index.html Language about an implementation report has been removed, and the only substantive modification from the previous proposed draft is that referenc