- From: ashok malhotra <ashok.malhotra@oracle.com>
- Date: Tue, 20 Dec 2011 06:11:23 -0800
- To: www-tag@w3.org
Jonathan: IIRC, there was some conflict between CORS and UMP. Should look at that again? All the best, Ashok On 12/19/2011 7:23 PM, Noah Mendelsohn wrote: > Thank you Jonathan. I've looked a bit at CORS, and even wrote a simple toy app that wound up using it. > > Question: are we at a point where we can net out what, if anything, are likely areas of concern for the TAG regarding CORS? I remember that we had detailed discussions over a year ago, but no longer recall whether we had particular concerns, or just a sense that CORS is a development that we should understand and track. Thank you. > > Noah > > On 12/19/2011 2:21 PM, Jonathan A Rees wrote: >> ACTION-344: Alert TAG chair when CORS and/or UMP goes to LC to trigger >> security review >> >> CORS hasn't gone to LC yet, but I wanted to attach this email to the >> tracker log for this action, as it appears to be immanent. >> >> Jonathan >> >> ---------- Forwarded message ---------- >> From: Hill, Brad<bhill@paypal-inc.com> >> Date: Mon, Dec 19, 2011 at 1:40 PM >> Subject: CfC: CORS to advance to Last Call >> To: "public-webappsec@w3.org"<public-webappsec@w3.org>, "WebApps WG >> (public-webapps@w3.org)"<public-webapps@w3.org> >> >> As discussed in the WebAppSec WG call on Dec 6, the editor would like >> to promote Cross-Origin Resource Sharing (CORS) to Last Call and this >> is a Call for Consensus to do so: >> >> >> >> http://www.w3.org/TR/2010/WD-cors-20100727/ >> >> >> >> This CfC satisfies the group's requirement to "record the group's >> decision to request advancement". >> >> >> >> Positive response to this CfC is preferred and encouraged and silence >> will be considered as agreement with the proposal. The deadline for >> comments is January 3, 2012. Please send all comments to: >> >> >> >> public-webappsec@w3.org >> >> >> >> Thank you, >> >> >> >> Brad Hill >> >> >
Received on Tuesday, 20 December 2011 14:11:20 UTC