ACTION-331: Consider ways to track the 'confused deputy problem' issue in webapps/cors
Consider ways to track the 'confused deputy problem' issue in webapps/cors
- State:
- closed
- Person:
- Dan Connolly
- Due on:
- November 24, 2009
- Created on:
- November 10, 2009
- Associated Product:
- Web Application Architecture
- Related emails:
- Re: Agenda and required reading for the 8-10 December 2009 TAG F2F (from noah_mendelsohn@us.ibm.com on 2009-12-07)
- Re: Agenda and required reading for the 8-10 December 2009 TAG F2F (from noah_mendelsohn@us.ibm.com on 2009-12-03)
- Agenda and required reading for the 8-10 December 2009 TAG F2F (from noah_mendelsohn@us.ibm.com on 2009-12-02)
- Re: 'Uniform Messaging, a CSRF resistant profile of CORS' (from jar@creativecommons.org on 2009-11-25)
- agenda for TAG meeting 8-10 Dec (from connolly@w3.org on 2009-11-25)
- 'Uniform Messaging, a CSRF resistant profile of CORS' (from connolly@w3.org on 2009-11-24)
Related notes:
[DanC]: http://www.w3.org/2008/webapps/track/issues/108 from http://www.w3.org/2009/11/02-webapps-minutes.html#item03
10 Nov 2009, 16:47:28[DanC]: cf http://www.w3.org/html/wg/tracker/issues/37
11 Nov 2009, 04:11:09oops; never mind the pointer to html/wg/tracker/issues/37
Dan Connolly, 11 Nov 2009, 04:11:53ping Mike to see how close CORS is to last call ~1Dec
Dan Connolly, 12 Nov 2009, 22:01:12Display change log.