Wednesday, 30 June 2004
- Re: Call for consensus on UNLOCK Request-URI being lock root
- Re: Call for consensus on UNLOCK Request-URI being lock root
- Re: LOCK error marshalling (lockdiscovery property included?)
- Re: Call for consensus on UNLOCK Request-URI being lock root
- Re: Issue #44: REPORT_OTHER_RESOURCE_LOCKED
- Re: Call for consensus on UNLOCK Request-URI being lock root
- Re: LOCK error marshalling (lockdiscovery property included?)
- Re: Issue #44: REPORT_OTHER_RESOURCE_LOCKED
- Re: Call for consensus on UNLOCK Request-URI being lock root
- Re: Call for consensus on UNLOCK Request-URI being lock root
- Re: ID: draft-ietf-webdav-bind-05
- [Fwd: I-D ACTION:draft-reschke-webdav-locking-04.txt]
Tuesday, 29 June 2004
- Re: Summary on LOCKS_SHOULD_THEY_USE_AN_IF_HEADER_TO_VERIFY
- Re: Summary on LOCKS_SHOULD_THEY_USE_AN_IF_HEADER_TO_VERIFY
Sunday, 27 June 2004
- Re: Call for consensus on UNLOCK Request-URI being lock root
- Re: Call for consensus on UNLOCK Request-URI being lock root
Saturday, 26 June 2004
Thursday, 24 June 2004
- Re: Issue #44: REPORT_OTHER_RESOURCE_LOCKED
- Re: WebDav
- WebDav
- Re: Issue #44: REPORT_OTHER_RESOURCE_LOCKED
- Re: Issue #66: MUST_AN_IF_HEADER_CHECK_THE_ROOT_OF_URL
- Re: Issue #44: REPORT_OTHER_RESOURCE_LOCKED
Wednesday, 23 June 2004
- Re: Issue 2.5_language, was: ID: draft-ietf-webdav-bind-05
- Re: Issue 2.5_language, was: ID: draft-ietf-webdav-bind-05
- Re: Issue 2.5_language, was: ID: draft-ietf-webdav-bind-05
- Re: Issue 2.5_language, was: ID: draft-ietf-webdav-bind-05
- Re: ID: draft-ietf-webdav-bind-05
- Re: Issue 2.5_language, was: ID: draft-ietf-webdav-bind-05
- Re: ID: draft-ietf-webdav-bind-05
- Re: Issue 2.5_language, was: ID: draft-ietf-webdav-bind-05
- Re: Issue 2.5_language, was: ID: draft-ietf-webdav-bind-05
- Re: ID: draft-ietf-webdav-bind-05
- Re: ID: draft-ietf-webdav-bind-05
- Re: ID: draft-ietf-webdav-bind-05
- Re: Issue 2.5_language, was: ID: draft-ietf-webdav-bind-05
- Re: ID: draft-ietf-webdav-bind-05
- Re: ID: draft-ietf-webdav-bind-05
- Re: Issue 2.5_language, was: ID: draft-ietf-webdav-bind-05
- Re: ID: draft-ietf-webdav-bind-05
- Issue 2.5_language, was: ID: draft-ietf-webdav-bind-05
- Re: ID: draft-ietf-webdav-bind-05
- Re: ID: draft-ietf-webdav-bind-05
- Re: ID: draft-ietf-webdav-bind-05
- Re: ID: draft-ietf-webdav-bind-05
- Re: ID: draft-ietf-webdav-bind-05
- Re: ID: draft-ietf-webdav-bind-05
- ID: draft-ietf-webdav-bind-05
Tuesday, 22 June 2004
Monday, 21 June 2004
- Re: Call for consensus on UNLOCK Request-URI being lock root
- Re: Call for consensus on UNLOCK Request-URI being lock root
- Status of RFC2518bis
- Call for consensus on UNLOCK Request-URI being lock root
- Re: Issue 079_UNLOCK_BY_NON_LOCK_OWNER
- Re: Issue 079_UNLOCK_BY_NON_LOCK_OWNER
- Re: AW: new auto-version value
- AW: new auto-version value
Sunday, 20 June 2004
Saturday, 19 June 2004
Friday, 18 June 2004
- Issue #44: REPORT_OTHER_RESOURCE_LOCKED
- Issue #66: MUST_AN_IF_HEADER_CHECK_THE_ROOT_OF_URL
- Re: new auto-version value
- new auto-version value
- Re: resolving 057_LOCK_SEMANTICS
- Re: resolving 057_LOCK_SEMANTICS
Thursday, 17 June 2004
- DRAFT schedule: Meeting Thurs, Aug 5 -- afternoon
- Fwd: Last Call: 'HTTP adaptation with OPES' to Proposed Standard
- resolving 057_LOCK_SEMANTICS
Tuesday, 15 June 2004
- Re: FW: [Moderator Action] How does WebDAV handles caching ?
- FW: [Moderator Action] How does WebDAV handles caching ?
- FW: WebDAV via squid-2.5
- Re: Issue #68: UNLOCK_WITHOUT_GOOD_TOKEN
- Re: Resolve Issue 67 UNLOCK_NEEDS_IF_HEADER
- Resolve Issue 67 UNLOCK_NEEDS_IF_HEADER
Monday, 14 June 2004
- GULP 5.8, was: GULP 5.7, was: GULP 5.6 vs issue UNLOCK_WHAT_URL (65)
- Re: GULP 5.7, was: GULP 5.6 vs issue UNLOCK_WHAT_URL (65)
- Re: new DELETE vs collection lock issue
- new DELETE vs collection lock issue
- Re: GULP 5.7, was: GULP 5.6 vs issue UNLOCK_WHAT_URL (65)
- GULP 5.7, was: GULP 5.6 vs issue UNLOCK_WHAT_URL (65)
Saturday, 12 June 2004
Friday, 11 June 2004
Wednesday, 9 June 2004
Tuesday, 8 June 2004
- Re: LOCK error marshalling (lockdiscovery property included?)
- Re: Issue #68: UNLOCK_WITHOUT_GOOD_TOKEN
Monday, 7 June 2004
- Re: Issue #68: UNLOCK_WITHOUT_GOOD_TOKEN
- Re: LOCK error marshalling (lockdiscovery property included?)
- Re: Issue #68: UNLOCK_WITHOUT_GOOD_TOKEN
- RE: Announcement of new co-chair
- Re: LOCK error marshalling (lockdiscovery property included?)
- Re: Issue #68: UNLOCK_WITHOUT_GOOD_TOKEN
- Meeting planning (was: Re: Announcement of new co-chair)
- Announcement of new co-chair
- Re: Issue #68: UNLOCK_WITHOUT_GOOD_TOKEN
- Re: Issue #68: UNLOCK_WITHOUT_GOOD_TOKEN
- Re: Issue #68: UNLOCK_WITHOUT_GOOD_TOKEN
- Re: Issue #68: UNLOCK_WITHOUT_GOOD_TOKEN
Sunday, 6 June 2004
Saturday, 5 June 2004
- Re: LOCK error marshalling (lockdiscovery property included?)
- Issue DEEP_LOCK_ERROR_STATUS
- Re: LOCK error marshalling (lockdiscovery property included?)
Friday, 4 June 2004
- Re: LOCK error marshalling (lockdiscovery property included?)
- LOCK error marshalling (lockdiscovery property included?)
- Re: AW: New Methods (was: Locking spec)
- AW: New Methods (was: Locking spec)
Thursday, 3 June 2004
- New Methods (was: Locking spec)
- Re: Locking spec
- Re: Locking spec
- Locking spec
- Summary on LOCKS_SHOULD_THEY_USE_AN_IF_HEADER_TO_VERIFY
- BIND spec progress, extracting LOCK from RFC2518(bis), was: [Fwd: I-D ACTION:draft-reschke-webdav-locking-01.txt]
Wednesday, 2 June 2004
- Re: LOCKS_SHOULD_THEY_USE_AN_IF_HEADER_TO_VERIFY vs RFC2518bis-05
- Re: LOCKS_SHOULD_THEY_USE_AN_IF_HEADER_TO_VERIFY vs RFC2518bis-05
- Re: LOCKS_SHOULD_THEY_USE_AN_IF_HEADER_TO_VERIFY vs RFC2518bis-05
- Re: LOCKS_SHOULD_THEY_USE_AN_IF_HEADER_TO_VERIFY vs RFC2518bis-05
- Re: LOCKS_SHOULD_THEY_USE_AN_IF_HEADER_TO_VERIFY vs RFC2518bis-05
- Re: LOCKS_SHOULD_THEY_USE_AN_IF_HEADER_TO_VERIFY vs RFC2518bis-05
- Re: LOCKS_SHOULD_THEY_USE_AN_IF_HEADER_TO_VERIFY vs RFC2518bis-05
- Re: LOCKS_SHOULD_THEY_USE_AN_IF_HEADER_TO_VERIFY vs RFC2518bis-05
- Re: LOCKS_SHOULD_THEY_USE_AN_IF_HEADER_TO_VERIFY vs RFC2518bis-05
- Re: LOCKS_SHOULD_THEY_USE_AN_IF_HEADER_TO_VERIFY vs RFC2518bis-05
- Re: LOCKS_SHOULD_THEY_USE_AN_IF_HEADER_TO_VERIFY vs RFC2518bis-05
- LOCKS_SHOULD_THEY_USE_AN_IF_HEADER_TO_VERIFY vs RFC2518bis-05
Tuesday, 1 June 2004
Monday, 31 May 2004
- Re: GULP 5.6 vs issue UNLOCK_WHAT_URL (65)
- Re: Issue 60: LOCK_REFRESH_BODY
- Re: Issue 60: LOCK_REFRESH_BODY
- Re: GULP 5.6 vs issue UNLOCK_WHAT_URL (65)
- Re: Issue 60: LOCK_REFRESH_BODY
- GULP 5.6 vs issue UNLOCK_WHAT_URL (65)
Thursday, 27 May 2004
Wednesday, 26 May 2004
Tuesday, 25 May 2004
Monday, 24 May 2004
- Issue 60: LOCK_REFRESH_BODY
- Issue 079_UNLOCK_BY_NON_LOCK_OWNER
- Re: [ACL] WebDAV Access Control Protocol published as RFC3744
Sunday, 23 May 2004
Saturday, 22 May 2004
Friday, 21 May 2004
- Re: FYI: I-D ACTION:draft-dusseault-http-patch-02.txt
- Re: FYI: I-D ACTION:draft-dusseault-http-patch-02.txt
Thursday, 20 May 2004
Wednesday, 19 May 2004
- WG Action: RECHARTER: WWW Distributed Authoring and Versioning (webdav)
- WG Action: RECHARTER: WWW Distributed Authoring and Versioning (webdav)
Wednesday, 12 May 2004
Tuesday, 11 May 2004
Monday, 10 May 2004
Saturday, 8 May 2004
Thursday, 6 May 2004
- Re: WebDAV Access Control Protocol published as RFC3744
- WebDAV Access Control Protocol published as RFC3744
Wednesday, 5 May 2004
Tuesday, 4 May 2004
- Re: Another issue on SASL draft
- list item separator
- Re: RFC2518 issues IF_AND_AUTH and LOCK_SEMANTICS
Monday, 3 May 2004
- Fw: Goliath question
- Fw: PROPFIND with just property names not working thro' telnet on port 80
- Another issue on SASL draft
- Re: HTTP sasl draft in last call
- Re: RFC2518 issues IF_AND_AUTH and LOCK_SEMANTICS
- Re: RFC2518 issues IF_AND_AUTH and LOCK_SEMANTICS
Sunday, 2 May 2004
- Re: RFC2518 issues IF_AND_AUTH and LOCK_SEMANTICS
- Re (2): summary of BIND/RFC2518 status
- Re: summary of BIND/RFC2518 status
- Re: summary of BIND/RFC2518 status
Friday, 30 April 2004
Wednesday, 28 April 2004
- Re: RFC2518 issues IF_AND_AUTH and LOCK_SEMANTICS
- Re: RFC2518 issues IF_AND_AUTH and LOCK_SEMANTICS
- Re: RFC2518 issues IF_AND_AUTH and LOCK_SEMANTICS
- Re: RFC2518 issues IF_AND_AUTH and LOCK_SEMANTICS
- Re: RFC2518 issues IF_AND_AUTH and LOCK_SEMANTICS
- Re: RFC2518 issues IF_AND_AUTH and LOCK_SEMANTICS
- Re: RFC2518 issues IF_AND_AUTH and LOCK_SEMANTICS
- Re: RFC2518 issues IF_AND_AUTH and LOCK_SEMANTICS
- Re: RFC2518 issues IF_AND_AUTH and LOCK_SEMANTICS
- Re: RFC2518 issues IF_AND_AUTH and LOCK_SEMANTICS
- Re: RFC2518 issues IF_AND_AUTH and LOCK_SEMANTICS
- Mark Nottingham on "Using WebDAV as a Description Format for REST"
Sunday, 25 April 2004
Wednesday, 21 April 2004
Tuesday, 20 April 2004
Monday, 19 April 2004
- Re: [ACL] Re: Last minute ACL stuff (was DAV:unauthenticated usage)
- Re: [ACL] Re: Last minute ACL stuff (was DAV:unauthenticated usage)
- Re: [ACL] Re: Last minute ACL stuff (was DAV:unauthenticated usage)
- Re: [ACL] Re: Last minute ACL stuff (was DAV:unauthenticated usage)
- Re: [ACL] Re: Last minute ACL stuff (was DAV:unauthenticated usage)
- ACL spec enters RFC-Editors "AUTH48" period
Sunday, 18 April 2004
- Re: [ACL] Re: Last minute ACL stuff (was DAV:unauthenticated usage)
- Re: HELP: only -ONE- client LOCK/UNLOCK's my WebDAV served files, -ALL- others issue GET
- HELP: only -ONE- client LOCK/UNLOCK's my WebDAV served files, -ALL- others issue GET
Tuesday, 13 April 2004
- Re: Remaining issues with the bind draft -- process
- Re: [ACL] DAV:unauthenticated usage
- Re: set a property with an empty content
- Re: set a property with an empty content
Monday, 12 April 2004
Sunday, 11 April 2004
Friday, 9 April 2004
Wednesday, 7 April 2004
- Re: Re (2): Status of RFC2518Bis
- Re: Re (2): Status of RFC2518Bis
- Re: Re (2): Status of RFC2518Bis
- Re: Re (2): Status of RFC2518Bis
- Re: Re (2): Status of RFC2518Bis
- Re: Re (2): Status of RFC2518Bis
Tuesday, 6 April 2004
- Re: Status of RFC2518Bis (Was Re: Remaining issues with the bind draft -- process)
- Re: Status of RFC2518Bis (Was Re: Remaining issues with the bind draft -- process)
- Re (2): Status of RFC2518Bis
- Re: Status of RFC2518Bis (Was Re: Remaining issues with the bind draft -- process)
- Status of RFC2518Bis (Was Re: Remaining issues with the bind draft -- process)
- Re: I-D ACTION:draft-ietf-webdav-redirectref-protocol-08.txt
- I-D ACTION:draft-ietf-webdav-redirectref-protocol-08.txt
- Re: Remaining issues with the bind draft -- process
- Re: Remaining issues with the bind draft -- process
- Re: Remaining issues with the bind draft -- process
- Re: Remaining issues with the bind draft -- process
- Re: Remaining issues with the bind draft -- process
- Re: Remaining issues with the bind draft -- process
- Re: Remaining issues with the bind draft -- process
- Re: Remaining issues with the bind draft -- process
Monday, 5 April 2004
- Re: Remaining issues with the bind draft -- process
- Re: Remaining issues with the bind draft -- process
- Re: Remaining issues with the bind draft -- process
- Re: What is actually locked?
- Re (2): What is actually locked?
- Re: Remaining issues with the bind draft -- process
- Re: Remaining issues with the bind draft -- process
- Re: Remaining issues with the bind draft -- process
- Re: Remaining issues with the bind draft -- process
- Re: Remaining issues with the bind draft -- process
- Re: What is actually locked?
- Re: Remaining issues with the bind draft -- process
- Re: Remaining issues with the bind draft -- process
- Re: Remaining issues with the bind draft -- process
- Re: What is actually locked?
- Re: What is actually locked?
- Re: Remaining issues with the bind draft -- process
- Re: What is actually locked?
- Re: Remaining issues with the bind draft -- process
- What is actually locked?
- Remaining issues with the bind draft -- process
- Work of a co-chair - bind spec
- Re: What is left after LOCK/UNLOCK on null resource?
- Re: Please submit last call on draft-ietf-webdav-bind-05.txt
- Re: Please submit last call on draft-ietf-webdav-bind-05.txt