public-appformats@w3.org from February 2008 by author

Anne van Kesteren

• Re: To cookie or not to cookie (Tuesday, 26 February)
• Re: Access Control for Cross-site Requests WD Published (Monday, 25 February)
• Re: Cross-site Requests and Custom HTTP Headers (Monday, 25 February)
• Re: Cross-site Requests and Custom HTTP Headers (Monday, 25 February)
• Re: Spoofing the Access-Control-Origin in existing browsers (Monday, 25 February)
• Re: Should Access-Control-Origin match postMessage port behavior? (Saturday, 23 February)
• Re: CSR and Mozilla - Clarifying HTTP Header Filtering (Thursday, 21 February)
• Cross-site Requests and Custom HTTP Headers (Wednesday, 20 February)
• Re: Access Control for Cross-site Requests WD Published (Wednesday, 20 February)
• Re: CSR and Mozilla - Clarifying HTTP Header Filtering (Wednesday, 20 February)
• Re: CSR and Mozilla - Clarifying HTTP Header Filtering (Wednesday, 20 February)
• Re: Access Control for Cross-site Requests WD Published (Tuesday, 19 February)
• Re: CSR and Mozilla - Clarifying HTTP Header Filtering (Tuesday, 19 February)
• Re: CSR and Mozilla - Clarifying HTTP Header Filtering (Tuesday, 19 February)
• Re: Access Control for Cross-site Requests WD Published (Tuesday, 19 February)
• Re: CSR and Mozilla - Clarifying HTTP Header Filtering (Tuesday, 19 February)
• Re: Access Control for Cross-site Requests WD Published (Monday, 18 February)
• Access Control for Cross-site Requests WD Published (Friday, 15 February)
• Re: Accountability in AC4CSR (Thursday, 14 February)
• Re: Accountability in AC4CSR (Thursday, 14 February)
• Re: Specifying auth credentials and access-control (Wednesday, 13 February)
• Re: Specifying auth credentials and access-control (Monday, 11 February)
• Re: Proposal for ... POST when dealing with large numbers of URIs (Sunday, 10 February)
• Re: Proposal for ... POST when dealing with large numbers of URIs (Sunday, 10 February)
• Re: Proposal for ... POST when dealing with large numbers of URIs (Saturday, 9 February)
• Re: Simplifying the AC spec (Saturday, 9 February)
• Re: Simplifying the AC spec (Saturday, 9 February)
• Re: Proposal for ... POST when dealing with large numbers of URIs (Saturday, 9 February)
• Re: <?access-control?> processing (Friday, 8 February)
• Re: <?access-control?> processing (Friday, 8 February)
• Re: IE Team's Feedback on the XHR Draft (Thursday, 7 February)
• Re: Accountability in AC4CSR (Thursday, 7 February)
• Re: Accountability in AC4CSR (Thursday, 7 February)
• Re: Accountability in AC4CSR (Thursday, 7 February)
• Re: [access-control] Forms WG comments on Access Control WD (Thursday, 7 February)
• Re: Accountability in AC4CSR (Thursday, 7 February)
• Re: Accountability in AC4CSR (Wednesday, 6 February)
• Re: Proposal for ... POST when dealing with large numbers of URIs (Wednesday, 6 February)
• Re: review of http://dev.w3.org/2006/waf/access-control/#requirements (Wednesday, 6 February)
• Re: Agenda for 6 February 2008 Voice Conference (Tuesday, 5 February)
• Re: Proposal for ... POST when dealing with large numbers of URIs (Tuesday, 5 February)
• Re: Proposal for ... POST when dealing with large numbers of URIs (Tuesday, 5 February)
• Re: Proposal for ... POST when dealing with large numbers of URIs (Tuesday, 5 February)
• Re: Proposal for ... POST when dealing with large numbers of URIs (Tuesday, 5 February)
• Re: redirect model for non-GET requests (Tuesday, 5 February)
• Re: Proposal for ... POST when dealing with large numbers of URIs (Monday, 4 February)
• Re: Proposal for a way to avoid a round-trip on every POST when dealing with large numbers of URIs (Monday, 4 February)
• Re: Requirement 10 (Monday, 4 February)
• Re: On Requirement 9 and "deny" (Monday, 4 February)
• Re: ACTION-161: Rewording for requirement 3 (Monday, 4 February)
• Re: [access-control] Requirement #5 (Monday, 4 February)
• Re: ACTION-158: Input for requirement 1.1 (Monday, 4 February)
• Re: ACTION-165: New wording for requirement 12 (Monday, 4 February)
• Re: ACTION-162: Suggested new wording for requirement 4 (Monday, 4 February)
• Re: Req 1.2 (Monday, 4 February)
• method check result cache? (was: Re: Review of 22 Jan editor's draft) (Monday, 4 February)
• Re: Review of 22 Jan editor's draft (Monday, 4 February)
• Re: redirect model for non-GET requests (Monday, 4 February)
• Re: redirect model for non-GET requests (Saturday, 2 February)
• Re: Proposal for a way to avoid a round-trip on every POST when dealing with large numbers of URIs (Saturday, 2 February)

Arthur Barstow

• Access Control Spec and Cookies (Friday, 29 February)
• Agenda for 27 Feb 2008 AC4CSR Voice Conf (Tuesday, 26 February)
• Access Control voice conf on Feb 20 is CANCELLED (Monday, 18 February)
• [widgets] Minutes from 14 February 2008 Widgets Voice Conf (Friday, 15 February)
• Minutes from 6 February 2008 Voice Conference (Wednesday, 6 February)
• Agenda for 6 February 2008 Voice Conference (Monday, 4 February)
• Re: Proposal for a way to avoid a round-trip on every POST when dealing with large numbers of URIs (Friday, 1 February)

Brad Porter

• Re: To cookie or not to cookie (Tuesday, 26 February)
• Re: To cookie or not to cookie (Tuesday, 26 February)
• Re: To cookie or not to cookie (Saturday, 23 February)
• Re: Mozilla security review of Access Control (Saturday, 23 February)
• Re: Mozilla security review of Access Control (Saturday, 23 February)
• Re: Mozilla security review of Access Control (Saturday, 23 February)
• Re: To cookie or not to cookie (Friday, 22 February)
• RE: Mozilla security review of Access Control (Friday, 22 February)
• Re: To cookie or not to cookie (Friday, 22 February)
• Re: Simplifying the AC spec (Friday, 8 February)

Close, Tyler J.

• RE: Mozilla security review of Access Control (Friday, 22 February)
• RE: Mozilla security review of Access Control (Friday, 22 February)
• RE: Mozilla security review of Access Control (Thursday, 21 February)
• RE: Mozilla security review of Access Control (Thursday, 21 February)
• RE: Mozilla security review of Access Control (Thursday, 21 February)
• RE: Accountability in AC4CSR (Tuesday, 12 February)
• RE: Accountability in AC4CSR (Tuesday, 12 February)
• RE: Accountability in AC4CSR (Tuesday, 12 February)
• RE: Accountability in AC4CSR (Thursday, 7 February)
• RE: Accountability in AC4CSR (Thursday, 7 February)
• RE: Accountability in AC4CSR (Thursday, 7 February)
• RE: Accountability in AC4CSR (Thursday, 7 February)
• RE: Accountability in AC4CSR (Thursday, 7 February)
• RE: Accountability in AC4CSR (Thursday, 7 February)
• RE: Issue 22 closed (Thursday, 7 February)
• RE: Accountability in AC4CSR (Thursday, 7 February)
• RE: Accountability in AC4CSR (Thursday, 7 February)
• RE: Accountability in AC4CSR (Thursday, 7 February)
• RE: Accountability in AC4CSR (Thursday, 7 February)
• RE: Accountability in AC4CSR (Thursday, 7 February)
• RE: Accountability in AC4CSR (Thursday, 7 February)
• Accountability in AC4CSR (Wednesday, 6 February)
• RE: Proposal for a way to avoid a round-trip on every POST when dealing with large numbers of URIs (Friday, 1 February)

Collin Jackson

• Mixed content warnings for cross-site requests (Tuesday, 26 February)
• Spoofing the Access-Control-Origin in existing browsers (Monday, 25 February)
• Re: Should Access-Control-Origin match postMessage port behavior? (Saturday, 23 February)
• Should Access-Control-Origin match postMessage port behavior? (Saturday, 23 February)

Daniel Veditz

• Re: To cookie or not to cookie (Friday, 22 February)

David Orchard

• RE: Simplifying the AC spec (Friday, 8 February)
• RE: Issue 22 closed (Thursday, 7 February)
• Issue 22 closed (Wednesday, 6 February)

Elias Sinderson

• Allowed headers for CSR (was: Accountability in [...]) (Wednesday, 20 February)

Henri Sivonen

• Re: CSR and Mozilla - Clarifying HTTP Header Filtering (Wednesday, 20 February)
• Re: CSR and Mozilla - Clarifying HTTP Header Filtering (Wednesday, 20 February)
• Re: CSR and Mozilla - Clarifying HTTP Header Filtering (Tuesday, 19 February)
• Re: Accountability in AC4CSR (Friday, 8 February)

Ian Hickson

• Re: To cookie or not to cookie (Tuesday, 26 February)
• Re: To cookie or not to cookie (Friday, 22 February)
• RE: Mozilla security review of Access Control (Thursday, 21 February)
• Re: Rule breaking on the Web (Thursday, 21 February)
• RE: Mozilla security review of Access Control (Thursday, 21 February)
• RE: Mozilla security review of Access Control (Thursday, 21 February)
• Re: Mozilla security review of Access Control (Wednesday, 20 February)
• Re: Authorization vs. Authentication (was Re: Accountability in AC4CSR) (Saturday, 16 February)
• Re: Authorization vs. Authentication (was Re: Accountability in AC4CSR) (Friday, 15 February)
• Re: Authorization vs. Authentication (was Re: Accountability in AC4CSR) (Thursday, 14 February)
• Re: Authorization vs. Authentication (was Re: Accountability in AC4CSR) (Thursday, 14 February)
• Re: Authorization vs. Authentication (was Re: Accountability in AC4CSR) (Thursday, 14 February)
• Re: Accountability in AC4CSR (Wednesday, 13 February)
• Re: Accountability in AC4CSR (Wednesday, 13 February)
• Re: Accountability in AC4CSR (Wednesday, 13 February)
• Re: Accountability in AC4CSR (Wednesday, 13 February)
• Re: Accountability in AC4CSR (Tuesday, 12 February)
• RE: Accountability in AC4CSR (Tuesday, 12 February)
• RE: Accountability in AC4CSR (Tuesday, 12 February)
• Re: Proposal for ... POST when dealing with large numbers of URIs (Sunday, 10 February)
• Re: Proposal for ... POST when dealing with large numbers of URIs (Saturday, 9 February)
• Re: Proposal for a way to avoid a round-trip on every POST when dealing with large numbers of URIs (Friday, 8 February)
• RE: Accountability in AC4CSR (Friday, 8 February)
• Re: Simplifying the AC spec (Friday, 8 February)
• RE: Issue 22 closed (Thursday, 7 February)
• RE: Accountability in AC4CSR (Thursday, 7 February)
• RE: Accountability in AC4CSR (Thursday, 7 February)
• RE: Accountability in AC4CSR (Thursday, 7 February)
• RE: Accountability in AC4CSR (Thursday, 7 February)
• Re: Proposal for a way to avoid a round-trip on every POST when dealing with large numbers of URIs (Thursday, 7 February)
• Re: Proposal for ... POST when dealing with large numbers of URIs (Thursday, 7 February)
• Re: ACTION-161: Rewording for requirement 3 (Wednesday, 6 February)
• Re: review of http://dev.w3.org/2006/waf/access-control/#requirements (Wednesday, 6 February)

John

• Re: Accountability in AC4CSR (Wednesday, 6 February)
• Re: redirect model for non-GET requests (Monday, 4 February)

John Panzer

• Re: To cookie or not to cookie (Friday, 22 February)
• Re: Cross-site Requests and Custom HTTP Headers (Friday, 22 February)
• Re: CSR and Mozilla - Clarifying HTTP Header Filtering (Tuesday, 19 February)
• Re: Access Control for Cross-site Requests WD Published (Tuesday, 19 February)
• Re: Authorization vs. Authentication (was Re: Accountability in AC4CSR) (Saturday, 16 February)
• Re: Authorization vs. Authentication (was Re: Accountability in AC4CSR) (Friday, 15 February)
• Re: Authorization vs. Authentication (was Re: Accountability in AC4CSR) (Thursday, 14 February)
• Re: Authorization vs. Authentication (was Re: Accountability in AC4CSR) (Thursday, 14 February)
• Authorization vs. Authentication (was Re: Accountability in AC4CSR) (Thursday, 14 February)
• Re: Accountability in AC4CSR (Thursday, 14 February)
• Re: Accountability in AC4CSR (Thursday, 14 February)
• Re: Accountability in AC4CSR (Wednesday, 13 February)
• Re: Accountability in AC4CSR (Wednesday, 13 February)
• Re: Accountability in AC4CSR (Wednesday, 13 February)
• Re: Accountability in AC4CSR (Wednesday, 13 February)
• Re: Accountability in AC4CSR (Wednesday, 13 February)
• Re: OAuth (Tuesday, 12 February)
• Re: Accountability in AC4CSR (Tuesday, 12 February)
• Re: Proposal for ... POST when dealing with large numbers of URIs (Tuesday, 5 February)
• Re: Comments on: Access Control for Cross-site Requests (Tuesday, 5 February)
• Re: Comments on: Access Control for Cross-site Requests (Monday, 4 February)
• Re: Proposal for ... POST when dealing with large numbers of URIs (Monday, 4 February)

Jon Ferraiolo

• Re: CSR and Mozilla - Clarifying HTTP Header Filtering (Tuesday, 19 February)
• Re: Accountability in AC4CSR (Wednesday, 6 February)
• Re: Policy enforcement point (Monday, 4 February)
• Re: Policy enforcement point (Monday, 4 February)

Jonas Sicking

• Re: To cookie or not to cookie (Tuesday, 26 February)
• Re: To cookie or not to cookie (Tuesday, 26 February)
• Re: Cross-site Requests and Custom HTTP Headers (Tuesday, 26 February)
• Re: Mixed content warnings for cross-site requests (Tuesday, 26 February)
• Re: Mixed content warnings for cross-site requests (Tuesday, 26 February)
• Re: Mozilla security review of Access Control (Saturday, 23 February)
• Re: Mozilla security review of Access Control (Saturday, 23 February)
• Re: Mozilla security review of Access Control (Saturday, 23 February)
• Re: Mozilla security review of Access Control (Saturday, 23 February)
• Another mozilla security review (Friday, 22 February)
• Re: To cookie or not to cookie (Friday, 22 February)
• To cookie or not to cookie (Friday, 22 February)
• Re: Cross-site Requests and Custom HTTP Headers (Friday, 22 February)
• Re: Mozilla security review of Access Control (Friday, 22 February)
• Re: Rule breaking on the Web (Thursday, 21 February)
• Re: Fwd: Accountability in AC4CSR (Wednesday, 20 February)
• Re: CSR and Mozilla - Clarifying HTTP Header Filtering (Wednesday, 20 February)
• Re: CSR and Mozilla - Clarifying HTTP Header Filtering (Wednesday, 20 February)
• Re: Mozilla security review of Access Control (Wednesday, 20 February)
• Re: Mozilla security review of Access Control (Wednesday, 20 February)
• Re: CSR and Mozilla - Clarifying HTTP Header Filtering (Tuesday, 19 February)
• Re: Access Control for Cross-site Requests WD Published (Tuesday, 19 February)
• Re: CSR and Mozilla - Clarifying HTTP Header Filtering (Tuesday, 19 February)
• Mozilla security review of Access Control (Tuesday, 12 February)
• OAuth (Tuesday, 12 February)
• Re: Specifying auth credentials and access-control (Monday, 11 February)
• Specifying auth credentials and access-control (Monday, 11 February)
• Re: Proposal for ... POST when dealing with large numbers of URIs (Sunday, 10 February)
• Re: Proposal for a way to avoid a round-trip on every POST when dealing with large numbers of URIs (Friday, 8 February)
• Re: Simplifying the AC spec (Friday, 8 February)
• Re: Simplifying the AC spec (Friday, 8 February)
• Simplifying the AC spec (Friday, 8 February)
• Re: <?access-control?> processing (Friday, 8 February)
• <?access-control?> processing (Friday, 8 February)
• Re: Accountability in AC4CSR (Friday, 8 February)
• Re: [access-control] Forms WG comments on Access Control WD (Thursday, 7 February)
• Re: Accountability in AC4CSR (Thursday, 7 February)
• Re: Proposal for a way to avoid a round-trip on every POST when dealing with large numbers of URIs (Thursday, 7 February)
• Re: [access-control] Forms WG comments on Access Control WD (Thursday, 7 February)
• Re: Accountability in AC4CSR (Thursday, 7 February)
• Re: Accountability in AC4CSR (Thursday, 7 February)
• Re: review of http://dev.w3.org/2006/waf/access-control/#requirements (Thursday, 7 February)
• Re: Accountability in AC4CSR (Wednesday, 6 February)
• Re: Proposal for ... POST when dealing with large numbers of URIs (Wednesday, 6 February)
• Re: ACTION-161: Rewording for requirement 3 (Wednesday, 6 February)
• Re: Proposal for a way to avoid a round-trip on every POST when dealing with large numbers of URIs (Wednesday, 6 February)
• Re: ACTION-161: Rewording for requirement 3 (Wednesday, 6 February)
• Re: review of http://dev.w3.org/2006/waf/access-control/#requirements (Wednesday, 6 February)
• Re: Proposal for a way to avoid a round-trip on every POST when dealing with large numbers of URIs (Wednesday, 6 February)
• Re: review of http://dev.w3.org/2006/waf/access-control/#requirements (Wednesday, 6 February)
• Re: Agenda for 6 February 2008 Voice Conference (Tuesday, 5 February)
• Re: Comments on: Access Control for Cross-site Requests (Tuesday, 5 February)
• Re: Comments on: Access Control for Cross-site Requests (Tuesday, 5 February)
• Re: redirect model for non-GET requests (Tuesday, 5 February)
• Re: Comments on: Access Control for Cross-site Requests (Tuesday, 5 February)
• Re: redirect model for non-GET requests (Monday, 4 February)
• Re: Policy enforcement point (Monday, 4 February)
• Re: redirect model for non-GET requests (Monday, 4 February)
• Re: On Requirement 9 and "deny" (Monday, 4 February)
• Policy enforcement point (Sunday, 3 February)
• Re: Comments on: Access Control for Cross-site Requests (Friday, 1 February)
• ACTION-161: Rewording for requirement 3 (Friday, 1 February)

Klotz, Leigh

• RE: [access-control] Forms WG comments on Access Control WD (Thursday, 7 February)
• RE: [access-control] Forms WG comments on Access Control WD (Wednesday, 6 February)

Kris Zyp

• Re: Access Control for Cross-site Requests WD Published (Monday, 25 February)
• Re: Access Control for Cross-site Requests WD Published (Friday, 15 February)

L. David Baron

• Re: Accountability in AC4CSR (Wednesday, 6 February)
• Re: Policy enforcement point (Monday, 4 February)

Marc Silbey

• RE: Access Control Spec and Cookies (Friday, 29 February)

Marcos Caceres

• Re: comments on Widgets' spec (Friday, 22 February)
• Re: Widgets (Friday, 22 February)
• CfP: WISE 2008 Workshop on Mashups, Enterprise Mashups and Lightweight Composition on the Web (MEM&LCW 2008) (Friday, 22 February)
• Re: Access Control for Cross-site Requests WD Published (Monday, 18 February)
• [Widget specs] Some changes (Tuesday, 5 February)
• Re: Widget Security (Monday, 4 February)

Mark Baker

• Re: Rule breaking on the Web (Monday, 25 February)
• Re: Rule breaking on the Web (Monday, 25 February)
• Rule breaking on the Web (Thursday, 21 February)
• Re: CSR and Mozilla - Clarifying HTTP Header Filtering (Thursday, 21 February)
• Re: CSR and Mozilla - Clarifying HTTP Header Filtering (Wednesday, 20 February)
• Re: CSR and Mozilla - Clarifying HTTP Header Filtering (Wednesday, 20 February)
• Re: CSR and Mozilla - Clarifying HTTP Header Filtering (Wednesday, 20 February)
• Re: CSR and Mozilla - Clarifying HTTP Header Filtering (Wednesday, 20 February)
• Re: CSR and Mozilla - Clarifying HTTP Header Filtering (Tuesday, 19 February)
• Re: CSR and Mozilla - Clarifying HTTP Header Filtering (Tuesday, 19 February)

Mark Nottingham

• Re: review of http://dev.w3.org/2006/waf/access-control/#requirements (Wednesday, 6 February)
• review of http://dev.w3.org/2006/waf/access-control/#requirements (Tuesday, 5 February)

mike amundsen

• Re: Cross-site Requests and Custom HTTP Headers (Wednesday, 27 February)
• Re: Cross-site Requests and Custom HTTP Headers (Tuesday, 26 February)
• Re: To cookie or not to cookie (Saturday, 23 February)
• Re: Access Control for Cross-site Requests WD Published (Tuesday, 19 February)
• Re: CSR and Mozilla - Clarifying HTTP Header Filtering (Tuesday, 19 February)
• Re: CSR and Mozilla - Clarifying HTTP Header Filtering (Tuesday, 19 February)
• Re: CSR and Mozilla - Clarifying HTTP Header Filtering (Tuesday, 19 February)
• Re: Access Control for Cross-site Requests WD Published (Tuesday, 19 February)
• Re: CSR and Mozilla - Clarifying HTTP Header Filtering (Tuesday, 19 February)
• Re: Access Control for Cross-site Requests WD Published (Friday, 15 February)
• -- (Friday, 15 February)
• CSR and Mozilla - Clarifying HTTP Header Filtering (Friday, 15 February)
• Fwd: Accountability in AC4CSR (Thursday, 14 February)
• Re: Accountability in AC4CSR (Thursday, 14 February)

Pollington, David, VF-Group

• Widgets (Friday, 15 February)

Subbu Allamaraju

• Re: Proposal for a way to avoid a round-trip on every POST when dealing with large numbers of URIs (Monday, 4 February)

T.V Raman

• Re: Comments on: Access Control for Cross-site Requests (Friday, 1 February)

Thomas Roessler

• Minutes: WAF WG 2008-02-27 (Wednesday, 27 February)
• Re: To cookie or not to cookie (Tuesday, 26 February)
• Re: Mixed content warnings for cross-site requests (Tuesday, 26 February)
• Re: CSR and Mozilla - Clarifying HTTP Header Filtering (Tuesday, 19 February)
• Re: Access Control for Cross-site Requests WD Published (Monday, 18 February)
• Re: ACTION-161: Rewording for requirement 3 (Wednesday, 6 February)
• Re: method check result cache? (was: Re: Review of 22 Jan editor's draft) (Monday, 4 February)

Venezia Claudio

• comments on Widgets' spec (Friday, 15 February)

Last message date: Friday, 29 February 2008 22:29:32 UTC