- From: Arthur Barstow <Art.Barstow@nokia.com>
- Date: Sat, 18 Apr 2009 17:23:02 -0400
- To: ext Anne van Kesteren <annevk@opera.com>, Jonas Sicking <jonas@sicking.cc>
- Cc: WebApps WG <public-webapps@w3.org>
On Apr 13, 2009, at 6:35 PM, ext Anne van Kesteren wrote: > On Mon, 13 Apr 2009 15:18:42 +0200, Arthur Barstow > <art.barstow@nokia.com> > wrote: >> What are the next steps for moving CORS along the Rec track? >> >> There were two related "Raised" issues and earlier today I moved >> them to >> Open: >> >> http://www.w3.org/2008/webapps/track/products/7 >> >> Please feel free to respond on public-webapps. > > I commented on both those issues when they were raised (see "Related > Notes"). I don't think either of them is valid at this point. OK, that's what I thought. All - Anne believes these two issues [I-27] and [I-28] are addressed in the latest CORS ED [CORS] and thus should be closed. If you disagree with closing these two issues (short rationale is included in the "Related Notes" section of each issue's Changelog), please reply by April 24. > As per my latest status report redirects is still an issue and > Jonas told > me he'd e-mail something about that but he hasn't done that yet. I > don't > know of any other outstanding issue. (Arguably the Origin header is an > outstanding issue but I don't really see how we can rename it or > change it > at this point.) > > (For redirects I think we should make a 303 response on a preflight > request a network error and leave the draft unchanged for > everything else.) Jonas - please let us know your thoughts on the redirect issue. Anne - other than the redirects issue, are there any other open issues/actions that must be addressed before a LCWD is published? -Regards, Art Barstow [I-27] <http://www.w3.org/2008/webapps/track/issues/27> [I-28] <http://www.w3.org/2008/webapps/track/issues/28> [CORS] <http://dev.w3.org/2006/waf/access-control/>
Received on Saturday, 18 April 2009 21:24:15 UTC