Friday, 29 February 2008
Wednesday, 27 February 2008
Tuesday, 26 February 2008
- Re: To cookie or not to cookie
- Re: To cookie or not to cookie
- Re: To cookie or not to cookie
- Re: To cookie or not to cookie
- Re: To cookie or not to cookie
- Agenda for 27 Feb 2008 AC4CSR Voice Conf
- Re: To cookie or not to cookie
- Re: To cookie or not to cookie
- Re: Cross-site Requests and Custom HTTP Headers
- Re: Mixed content warnings for cross-site requests
- Re: Mixed content warnings for cross-site requests
- Re: Mixed content warnings for cross-site requests
- Re: Cross-site Requests and Custom HTTP Headers
- Mixed content warnings for cross-site requests
Monday, 25 February 2008
- Re: Access Control for Cross-site Requests WD Published
- Re: Access Control for Cross-site Requests WD Published
- Re: Cross-site Requests and Custom HTTP Headers
- Re: Cross-site Requests and Custom HTTP Headers
- Re: Rule breaking on the Web
- Re: Rule breaking on the Web
- Re: Spoofing the Access-Control-Origin in existing browsers
- Spoofing the Access-Control-Origin in existing browsers
Friday, 22 February 2008
Saturday, 23 February 2008
- Re: To cookie or not to cookie
- Re: Mozilla security review of Access Control
- Re: To cookie or not to cookie
- Re: Mozilla security review of Access Control
- Re: Should Access-Control-Origin match postMessage port behavior?
- Re: Should Access-Control-Origin match postMessage port behavior?
- Should Access-Control-Origin match postMessage port behavior?
- Re: Mozilla security review of Access Control
- Re: Mozilla security review of Access Control
- Re: Mozilla security review of Access Control
- Re: Mozilla security review of Access Control
- Re: Mozilla security review of Access Control
Friday, 22 February 2008
- Another mozilla security review
- Re: To cookie or not to cookie
- Re: To cookie or not to cookie
- RE: Mozilla security review of Access Control
- RE: Mozilla security review of Access Control
- Re: To cookie or not to cookie
- RE: Mozilla security review of Access Control
- Re: To cookie or not to cookie
- Re: To cookie or not to cookie
- To cookie or not to cookie
- Re: Cross-site Requests and Custom HTTP Headers
- Re: comments on Widgets' spec
- Re: Cross-site Requests and Custom HTTP Headers
- Re: Mozilla security review of Access Control
- Re: Widgets
- CfP: WISE 2008 Workshop on Mashups, Enterprise Mashups and Lightweight Composition on the Web (MEM&LCW 2008)
Thursday, 21 February 2008
- RE: Mozilla security review of Access Control
- RE: Mozilla security review of Access Control
- Re: Rule breaking on the Web
- Re: Rule breaking on the Web
- Rule breaking on the Web
- RE: Mozilla security review of Access Control
- RE: Mozilla security review of Access Control
- Re: CSR and Mozilla - Clarifying HTTP Header Filtering
- Re: CSR and Mozilla - Clarifying HTTP Header Filtering
- RE: Mozilla security review of Access Control
- RE: Mozilla security review of Access Control
Wednesday, 20 February 2008
- Cross-site Requests and Custom HTTP Headers
- Allowed headers for CSR (was: Accountability in [...])
- Re: Fwd: Accountability in AC4CSR
- Re: CSR and Mozilla - Clarifying HTTP Header Filtering
- Re: Mozilla security review of Access Control
- Re: CSR and Mozilla - Clarifying HTTP Header Filtering
- Re: CSR and Mozilla - Clarifying HTTP Header Filtering
- Re: CSR and Mozilla - Clarifying HTTP Header Filtering
- Re: CSR and Mozilla - Clarifying HTTP Header Filtering
- Re: CSR and Mozilla - Clarifying HTTP Header Filtering
- Re: Mozilla security review of Access Control
- Re: Access Control for Cross-site Requests WD Published
- Re: CSR and Mozilla - Clarifying HTTP Header Filtering
- Re: CSR and Mozilla - Clarifying HTTP Header Filtering
- Re: CSR and Mozilla - Clarifying HTTP Header Filtering
- Re: CSR and Mozilla - Clarifying HTTP Header Filtering
- Re: Mozilla security review of Access Control
Tuesday, 19 February 2008
- Re: CSR and Mozilla - Clarifying HTTP Header Filtering
- Re: Access Control for Cross-site Requests WD Published
- Re: Access Control for Cross-site Requests WD Published
- Re: CSR and Mozilla - Clarifying HTTP Header Filtering
- Re: CSR and Mozilla - Clarifying HTTP Header Filtering
- Re: CSR and Mozilla - Clarifying HTTP Header Filtering
- Re: CSR and Mozilla - Clarifying HTTP Header Filtering
- Re: CSR and Mozilla - Clarifying HTTP Header Filtering
- Re: CSR and Mozilla - Clarifying HTTP Header Filtering
- Re: CSR and Mozilla - Clarifying HTTP Header Filtering
- Re: CSR and Mozilla - Clarifying HTTP Header Filtering
- Re: Access Control for Cross-site Requests WD Published
- Re: CSR and Mozilla - Clarifying HTTP Header Filtering
- Re: CSR and Mozilla - Clarifying HTTP Header Filtering
- Re: CSR and Mozilla - Clarifying HTTP Header Filtering
- Re: Access Control for Cross-site Requests WD Published
- Re: CSR and Mozilla - Clarifying HTTP Header Filtering
- Re: CSR and Mozilla - Clarifying HTTP Header Filtering
- Re: Access Control for Cross-site Requests WD Published
- Re: Access Control for Cross-site Requests WD Published
- Re: CSR and Mozilla - Clarifying HTTP Header Filtering
Monday, 18 February 2008
- Access Control voice conf on Feb 20 is CANCELLED
- Re: Access Control for Cross-site Requests WD Published
- Re: Access Control for Cross-site Requests WD Published
- Re: Access Control for Cross-site Requests WD Published
Friday, 15 February 2008
Saturday, 16 February 2008
- Re: Authorization vs. Authentication (was Re: Accountability in AC4CSR)
- Re: Authorization vs. Authentication (was Re: Accountability in AC4CSR)
Friday, 15 February 2008
- Re: Access Control for Cross-site Requests WD Published
- Widgets
- Access Control for Cross-site Requests WD Published
- [widgets] Minutes from 14 February 2008 Widgets Voice Conf
- comments on Widgets' spec
- --
- CSR and Mozilla - Clarifying HTTP Header Filtering
- Re: Authorization vs. Authentication (was Re: Accountability in AC4CSR)
- Re: Authorization vs. Authentication (was Re: Accountability in AC4CSR)
Thursday, 14 February 2008
- Re: Authorization vs. Authentication (was Re: Accountability in AC4CSR)
- Re: Authorization vs. Authentication (was Re: Accountability in AC4CSR)
- Re: Authorization vs. Authentication (was Re: Accountability in AC4CSR)
- Re: Authorization vs. Authentication (was Re: Accountability in AC4CSR)
- Fwd: Accountability in AC4CSR
- Re: Authorization vs. Authentication (was Re: Accountability in AC4CSR)
- Authorization vs. Authentication (was Re: Accountability in AC4CSR)
- Re: Accountability in AC4CSR
- Re: Accountability in AC4CSR
- Re: Accountability in AC4CSR
- Re: Accountability in AC4CSR
- Re: Accountability in AC4CSR
Wednesday, 13 February 2008
- Re: Accountability in AC4CSR
- Re: Accountability in AC4CSR
- Re: Accountability in AC4CSR
- Re: Accountability in AC4CSR
- Re: Accountability in AC4CSR
- Re: Accountability in AC4CSR
- Re: Accountability in AC4CSR
- Re: Specifying auth credentials and access-control
- Re: Accountability in AC4CSR
- Re: Accountability in AC4CSR
Tuesday, 12 February 2008
- Re: OAuth
- Re: Accountability in AC4CSR
- Mozilla security review of Access Control
- OAuth
- Re: Accountability in AC4CSR
- RE: Accountability in AC4CSR
- RE: Accountability in AC4CSR
- RE: Accountability in AC4CSR
- RE: Accountability in AC4CSR
- RE: Accountability in AC4CSR
Monday, 11 February 2008
- Re: Specifying auth credentials and access-control
- Re: Specifying auth credentials and access-control
- Specifying auth credentials and access-control
Sunday, 10 February 2008
- Re: Proposal for ... POST when dealing with large numbers of URIs
- Re: Proposal for ... POST when dealing with large numbers of URIs
- Re: Proposal for ... POST when dealing with large numbers of URIs
- Re: Proposal for ... POST when dealing with large numbers of URIs
Saturday, 9 February 2008
- Re: Proposal for ... POST when dealing with large numbers of URIs
- Re: Proposal for ... POST when dealing with large numbers of URIs
- Re: Simplifying the AC spec
- Re: Simplifying the AC spec
- Re: Proposal for ... POST when dealing with large numbers of URIs
Friday, 8 February 2008
- Re: Proposal for a way to avoid a round-trip on every POST when dealing with large numbers of URIs
- Re: Proposal for a way to avoid a round-trip on every POST when dealing with large numbers of URIs
- Re: Simplifying the AC spec
- RE: Accountability in AC4CSR
- Re: Simplifying the AC spec
- RE: Simplifying the AC spec
- Re: Simplifying the AC spec
- Re: Simplifying the AC spec
- Re: <?access-control?> processing
- Simplifying the AC spec
- Re: <?access-control?> processing
- Re: <?access-control?> processing
- <?access-control?> processing
- Re: Accountability in AC4CSR
- Re: Accountability in AC4CSR
Thursday, 7 February 2008
- RE: Accountability in AC4CSR
- RE: Accountability in AC4CSR
- RE: Issue 22 closed
- RE: Accountability in AC4CSR
- RE: Accountability in AC4CSR
- Re: IE Team's Feedback on the XHR Draft
- RE: Accountability in AC4CSR
- RE: Issue 22 closed
- RE: Accountability in AC4CSR
- RE: Accountability in AC4CSR
- RE: Accountability in AC4CSR
- Re: [access-control] Forms WG comments on Access Control WD
- Re: Accountability in AC4CSR
- RE: Accountability in AC4CSR
- RE: Issue 22 closed
- Re: Accountability in AC4CSR
- RE: Accountability in AC4CSR
- RE: [access-control] Forms WG comments on Access Control WD
- RE: Accountability in AC4CSR
- Re: Accountability in AC4CSR
- RE: Accountability in AC4CSR
- Re: Accountability in AC4CSR
- Re: [access-control] Forms WG comments on Access Control WD
- Re: Accountability in AC4CSR
- Re: Proposal for a way to avoid a round-trip on every POST when dealing with large numbers of URIs
- Re: [access-control] Forms WG comments on Access Control WD
- RE: Accountability in AC4CSR
- Re: Proposal for a way to avoid a round-trip on every POST when dealing with large numbers of URIs
- Re: Proposal for ... POST when dealing with large numbers of URIs
- Re: Accountability in AC4CSR
- Re: Accountability in AC4CSR
- RE: Accountability in AC4CSR
- RE: Accountability in AC4CSR
- RE: Accountability in AC4CSR
- Re: review of http://dev.w3.org/2006/waf/access-control/#requirements
Wednesday, 6 February 2008
- Re: Accountability in AC4CSR
- RE: [access-control] Forms WG comments on Access Control WD
- Re: Accountability in AC4CSR
- Re: Accountability in AC4CSR
- Re: Accountability in AC4CSR
- Re: Accountability in AC4CSR
- Accountability in AC4CSR
- Issue 22 closed
- Minutes from 6 February 2008 Voice Conference
- Re: review of http://dev.w3.org/2006/waf/access-control/#requirements
- Re: Proposal for ... POST when dealing with large numbers of URIs
- Re: ACTION-161: Rewording for requirement 3
- Re: Proposal for ... POST when dealing with large numbers of URIs
- Re: Proposal for a way to avoid a round-trip on every POST when dealing with large numbers of URIs
- Re: ACTION-161: Rewording for requirement 3
- Re: review of http://dev.w3.org/2006/waf/access-control/#requirements
- Re: review of http://dev.w3.org/2006/waf/access-control/#requirements
- Re: ACTION-161: Rewording for requirement 3
- Re: ACTION-161: Rewording for requirement 3
- Re: review of http://dev.w3.org/2006/waf/access-control/#requirements
- Re: Proposal for a way to avoid a round-trip on every POST when dealing with large numbers of URIs
- Re: review of http://dev.w3.org/2006/waf/access-control/#requirements
Tuesday, 5 February 2008
- review of http://dev.w3.org/2006/waf/access-control/#requirements
- Re: Agenda for 6 February 2008 Voice Conference
- Re: Agenda for 6 February 2008 Voice Conference
- Re: Proposal for ... POST when dealing with large numbers of URIs
- Re: Comments on: Access Control for Cross-site Requests
- Re: Comments on: Access Control for Cross-site Requests
- Re: Proposal for ... POST when dealing with large numbers of URIs
- Re: Proposal for ... POST when dealing with large numbers of URIs
- Re: Comments on: Access Control for Cross-site Requests
- [Widget specs] Some changes
- Re: redirect model for non-GET requests
- Re: Comments on: Access Control for Cross-site Requests
- Re: Proposal for ... POST when dealing with large numbers of URIs
- Re: Proposal for ... POST when dealing with large numbers of URIs
- Re: redirect model for non-GET requests
Monday, 4 February 2008
- Re: redirect model for non-GET requests
- Re: Policy enforcement point
- Re: method check result cache? (was: Re: Review of 22 Jan editor's draft)
- Re: Policy enforcement point
- Re: Policy enforcement point
- Re: Policy enforcement point
- Re: Comments on: Access Control for Cross-site Requests
- Agenda for 6 February 2008 Voice Conference
- Re: Proposal for ... POST when dealing with large numbers of URIs
- Re: redirect model for non-GET requests
- Re: Proposal for a way to avoid a round-trip on every POST when dealing with large numbers of URIs
- Re: Proposal for ... POST when dealing with large numbers of URIs
- Re: Proposal for a way to avoid a round-trip on every POST when dealing with large numbers of URIs
- Re: Requirement 10
- Re: On Requirement 9 and "deny"
- Re: ACTION-161: Rewording for requirement 3
- Re: [access-control] Requirement #5
- Re: ACTION-158: Input for requirement 1.1
- Re: ACTION-165: New wording for requirement 12
- Re: ACTION-162: Suggested new wording for requirement 4
- Re: Req 1.2
- method check result cache? (was: Re: Review of 22 Jan editor's draft)
- Re: Review of 22 Jan editor's draft
- Re: redirect model for non-GET requests
- Re: redirect model for non-GET requests
- Re: Widget Security
- Re: On Requirement 9 and "deny"
Sunday, 3 February 2008
Saturday, 2 February 2008
- Re: redirect model for non-GET requests
- Re: Proposal for a way to avoid a round-trip on every POST when dealing with large numbers of URIs
Friday, 1 February 2008
- RE: Proposal for a way to avoid a round-trip on every POST when dealing with large numbers of URIs
- Re: Comments on: Access Control for Cross-site Requests
- Re: Comments on: Access Control for Cross-site Requests
- Re: Proposal for a way to avoid a round-trip on every POST when dealing with large numbers of URIs
- ACTION-161: Rewording for requirement 3