[access-control] Requirement #5
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: 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
On Requirement 9 and "deny"
Minutes from 30 January 2008 Voice Conference on Access Control
ACTION-158: Input for requirement 1.1
Requirement 11
ACTION-165: New wording for requirement 12
ACTION-162: Suggested new wording for requirement 4
Req 1.2
Fwd: [rest-discuss] W3C Working Group on Cross-Domain requests needs your feedback
Agenda for 30 January 2008 Voice Conference
[access-control] syntax is still suboptimal?
ISSUE-22 (ac4csr-webarch): The AC4CSR spec and "webarch" [Access Control]
- Re: ISSUE-22 (ac4csr-webarch): The AC4CSR spec and "webarch" [Access Control]
- RE: ISSUE-22 (ac4csr-webarch): The AC4CSR spec and "webarch" [Access Control]
ACTION-154: policy decision / enforcement points
- Re: ACTION-154: policy decision / enforcement points
- Re: ACTION-154: policy decision / enforcement points
Minutes from 23 January 2008 Voice Conference on Access Control
- time change for WAF WG telcons [was: Minutes from 23 January 2008 Voice Conference on Access Control]
Review of 22 Jan editor's draft
[access-control] Editorial comments on Requirements Appendix v1.137
- Re: [access-control] Editorial comments on Requirements Appendix v1.137
- Re: [access-control] Editorial comments on Requirements Appendix v1.137
Feedback on Access Control
- Re: Feedback on Access Control
- Re: Feedback on Access Control
- Re: Feedback on Access Control
- Re: Feedback on Access Control
- Re: Feedback on Access Control
- Re: Feedback on Access Control
- Re: Feedback on Access Control
- P3P - Feedback on Access Control
- Re: P3P - Feedback on Access Control
- Re: P3P - Feedback on Access Control
- Re: P3P - Feedback on Access Control
- Re: P3P - Feedback on Access Control
- Re: P3P - Feedback on Access Control
- RE: P3P - Feedback on Access Control
- RE: P3P - Feedback on Access Control
- RE: P3P - Feedback on Access Control
- Re: P3P - Feedback on Access Control
- RE: P3P - Feedback on Access Control
- Re: P3P - Feedback on Access Control
- RE: P3P - Feedback on Access Control
- RE: P3P - Feedback on Access Control
- RE: P3P - Feedback on Access Control
- RE: P3P - Feedback on Access Control
- Re: P3P - Feedback on Access Control
- RE: P3P - Feedback on Access Control
- Re: P3P - Feedback on Access Control
- Re: Feedback on Access Control
- Re: Feedback on Access Control
Agenda for 23 January 2008 Voice Conf
[fwd] common dns misconfiguration can lead to "same site" scripting (from: taviso@sdf.lonestar.org)
Access Control: integrated Requirements, Use Cases and FAQ
- Re: Access Control: integrated Requirements, Use Cases and FAQ
- RE: Access Control: integrated Requirements, Use Cases and FAQ
Access Control open/raised issues
[ac] Security concerns
Access control requirements
[waf] Minutes from 16 January 2008 Voice Conference on Access Control
linking pre-check to POST and other requests?
Use case for cross-site DELETE, PUT, ...?
Access-Control: Proposed restructuring
RE: Request for review on Access Control for Cross-site Requests
specification style; last call
[ac] XBL Use Case input
FAQ & Use Cases
<form> POST versus Access Control POST
[waf] Access Control Issue 19: Requirements document updated dated 20080114
ISSUE-21: What is the Security Model for the access-control spec? [Access Control]
Fwd: OPTIONS and Method-Check
Minutes from WAF WG's 9 January 2008 meeting
Re: More clarity about cookie handling
Re: OPTIONS and Method-Check
Comments on requirements document
RE: [waf] Draft of merged Web Apps WG charter available
Re: [waf] minutes from 9 January 2008 Voice Conf (fwd)
- RE: [waf] minutes from 9 January 2008 Voice Conf (fwd)
- [access-control] Requirements, UCs and design rationale [Was: Subject: Re: [waf] minutes from 9 January 2008 Voice Conf (fwd) ]
- Re: [waf] minutes from 9 January 2008 Voice Conf (fwd)
- Re: [waf] minutes from 9 January 2008 Voice Conf (fwd)
- Re: [waf] minutes from 9 January 2008 Voice Conf (fwd)
- Re: [waf] minutes from 9 January 2008 Voice Conf (fwd)
Examining the 'no server modification' requirement
- Re: Examining the 'no server modification' requirement
- Re: Examining the 'no server modification' requirement
- Re: Examining the 'no server modification' requirement
Review of http://www.w3.org/TR/2007/WD-access-control-20071126/
- Re: Review of http://www.w3.org/TR/2007/WD-access-control-20071126/
- Re: Review of http://www.w3.org/TR/2007/WD-access-control-20071126/
- Re: Review of http://www.w3.org/TR/2007/WD-access-control-20071126/
- Are Jon's comments from IBM, the OAA, citizen Jon, ...? [Was: Re: Review of http://www.w3.org/TR/2007/WD-access-control-20071126/]
- Re: Are Jon's comments from IBM, the OAA, citizen Jon, ...? [Was: Re: Review of http://www.w3.org/TR/2007/WD-access-control-20071126/]
- Re: Review of http://www.w3.org/TR/2007/WD-access-control-20071126/
ISSUE 19: Requirements and Usage Scenarios document
- Re: ISSUE 19: Requirements and Usage Scenarios document
- Re: ISSUE 19: Requirements and Usage Scenarios document
- Re: ISSUE 19: Requirements and Usage Scenarios document
- Re: ISSUE 19: Requirements and Usage Scenarios document
- Re: ISSUE 19: Requirements and Usage Scenarios document
- Re: ISSUE 19: Requirements and Usage Scenarios document
- Re: ISSUE 19: Requirements and Usage Scenarios document
- Re: ISSUE 19: Requirements and Usage Scenarios document
- Re: ISSUE 19: Requirements and Usage Scenarios document
- Re: ISSUE 19: Requirements and Usage Scenarios document
- Re: ISSUE 19: Requirements and Usage Scenarios document
- Re: ISSUE 19: Requirements and Usage Scenarios document
Re: [waf] New Charter proposal
ISSUE-20: Client and Server model [Access Control]
- Re: ISSUE-20: Client and Server model [Access Control]
- Re: ISSUE-20: Client and Server model [Access Control]
ISSUE-19: What are the Requirements, Design Principles and Use Cases? [Access Control]
ISSUE-18: Is JSONRequest an acceptable alternative to the current model? [Access Control]
- Re: ISSUE-18: Is JSONRequest an acceptable alternative to the current model? [Access Control]
- RE: ISSUE-18: Is JSONRequest an acceptable alternative to the current model? [Access Control]
- Re: ISSUE-18: Is JSONRequest an acceptable alternative to the current model? [Access Control]
- RE: ISSUE-18: Is JSONRequest an acceptable alternative to the current model? [Access Control]
- Re: ISSUE-18: Is JSONRequest an acceptable alternative to the current model? [Access Control]
- Re: ISSUE-18: Is JSONRequest an acceptable alternative to the current model? [Access Control]
Fwd: Comments on: Access Control for Cross-site Requests
Re: [widgets] Open Ajax Alliance
RE: Comments on: Access Control for Cross-site Requests
- RE: Comments on: Access Control for Cross-site Requests
- Re: Comments on: Access Control for Cross-site Requests
- RE: Comments on: Access Control for Cross-site Requests
- RE: Comments on: Access Control for Cross-site Requests
- Re: Comments on: Access Control for Cross-site Requests
- Re: Comments on: Access Control for Cross-site Requests
- RE: Comments on: Access Control for Cross-site Requests
- RE: Comments on: Access Control for Cross-site Requests
- RE: Comments on: Access Control for Cross-site Requests
- RE: Comments on: Access Control for Cross-site Requests
- Re: Comments on: Access Control for Cross-site Requests
- RE: Comments on: Access Control for Cross-site Requests
- RE: Comments on: Access Control for Cross-site Requests
- Re: Comments on: Access Control for Cross-site Requests
- Re: Comments on: Access Control for Cross-site Requests
- RE: Comments on: Access Control for Cross-site Requests