Monday, 30 September 2002
- RE: 55th IETF WG/BOF Scheduling - DRAFT Agenda
- RE: 55th IETF WG/BOF Scheduling - DRAFT Agenda
- FW: 55th IETF WG/BOF Scheduling - DRAFT Agenda
- Re: Interop issue: Proposal for fixing lock token provision
- RE: Interop issue: Proposal for fixing lock token provision
Friday, 27 September 2002
- RE: Interop issue: Proposal for fixing lock token provision
- RE: Issue: Requiring server to use / terminated URL for returned collections
Thursday, 26 September 2002
- RE: Required properties with no value [WAS: workspace property on res ources that aren't in workspaces]
- Required properties with no value [WAS: workspace property on res ources that aren't in workspaces]
Wednesday, 25 September 2002
- Re: Interop issue: Proposal for fixing lock token provision
- RE: Issue: Requiring server to use / terminated URL for returned collections
- Re: Interop issue: Proposal for fixing lock token provision
Tuesday, 24 September 2002
Monday, 23 September 2002
- RE: Issue: Requiring server to use / terminated URL for returned collections
- Re: Interop issue: how can clients force authentication?
- RE: comments on RFC2518bis-02, sec 13.16
- RE: XML in LOCK <owner> tag should be self-contained
- RE: comments on RFC2518bis-02, sec 13.16
- RE: comments on RFC2518bis-02, sec 13.16
- RE: Interop issue: how can clients force authentication?
- RE: XML in LOCK <owner> tag should be self-contained
- Re: ETags, was: Issues from Interop/Interim WG Meeting
- RE: Interop issue: how can clients force authentication?
Sunday, 22 September 2002
- RE: comments on RFC2518bis-02, sec 13.16
- RE: comments on RFC2518bis-02, sec 6.3
- RE: comments on RFC2518bis-02, sec 13.16
- Re: comments on RFC2518bis-02, sec 6.3
- Re: comments on RFC2518bis-02, sec 13.16
Friday, 20 September 2002
- RE: XML in LOCK <owner> tag should be self-contained
- comments on RFC2518bis-02
- XML in LOCK <owner> tag should be self-contained
- RE: Interop issue: how can clients force authentication?
- RE: Interop issue: how can clients force authentication?
- Re: Interop issue: how can clients force authentication?
Thursday, 19 September 2002
- Re: Interop issue: how can clients force authentication?
- RE: ETags, was: Issues from Interop/Interim WG Meeting
- Re: I-D ACTION:draft-ietf-webdav-rfc2518bis-02.txt
Wednesday, 18 September 2002
- RE: ETags, was: Issues from Interop/Interim WG Meeting
- RE: Interop issue: how can clients force authentication?
- RE: ETags, was: Issues from Interop/Interim WG Meeting
- RE: ETags, was: Issues from Interop/Interim WG Meeting
- RE: ETags, was: Issues from Interop/Interim WG Meeting
- RE: ETags, was: Issues from Interop/Interim WG Meeting
- Re: Interop issue: how can clients force authentication?
- Re: ETags, was: Issues from Interop/Interim WG Meeting
- Re: ETags, was: Issues from Interop/Interim WG Meeting
- Re: Digest authentication
- Re: Digest authentication
- property registry, was: Notes for Sept 9 WG meeting (by Dennis Hamilton) - HTML Available
- RE: I-D ACTION:draft-ietf-webdav-rfc2518bis-02.txt
- RE: Interop issue: how can clients force authentication?
- RE: I-D ACTION:draft-ietf-webdav-rfc2518bis-02.txt
- RE: I-D ACTION:draft-ietf-webdav-rfc2518bis-02.txt
- I-D ACTION:draft-ietf-webdav-rfc2518bis-02.txt
- RE: I-D ACTION:draft-ietf-webdav-rfc2518bis-02.txt
- RE: Interop issue: how can clients force authentication?
- RE: Interop issue: how can clients force authentication?
- RE: Issue: Requiring server to use / terminated URL for returned collections
- Re: Issue: Requiring server to use / terminated URL for returned collections
- RE: I-D ACTION:draft-ietf-webdav-rfc2518bis-02.txt
- I-D ACTION:draft-ietf-webdav-rfc2518bis-02.txt
- Re: Digest authentication
- RE: Interop issue: how can clients force authentication?
- Re: Interop issue: how can clients force authentication?
- RE: ETags, was: Issues from Interop/Interim WG Meeting
- Re: Interop issue: how can clients force authentication?
- Re: Interop issue: how can clients force authentication?
- Re: ETags, was: Issues from Interop/Interim WG Meeting
- Re: ETags, was: Issues from Interop/Interim WG Meeting
- RE: Interop issue: how can clients force authentication?
- RE: Interop issue: how can clients force authentication?
- RE: Interop issue: how can clients force authentication?
- RE: ETags, was: Issues from Interop/Interim WG Meeting
- RE: Interop issue: how can clients force authentication?
- RE: Interop issue: how can clients force authentication?
- Re: Interop issue: how can clients force authentication?
- Re: Interop issue: Can we require clients to accept cookies?
- Digest authentication
- Re: ETags, was: Issues from Interop/Interim WG Meeting
- Re: Interop issue: how can clients force authentication?
Tuesday, 17 September 2002
- RE: Interop issue: how can clients force authentication?
- RE: extending the DAV: HTTP header, was: Issues from Interop/Inte rim WG Meeting
- Re: Interop issue: how can clients force authentication?
- RE: Issue: Requiring server to use / terminated URL for returned collections
- New RFC2518 bis draft
- RE: extending the DAV: HTTP header, was: Issues from Interop/Inte rim WG Meeting
- RE: Interop issue: how can clients force authentication?
- RE: extending the DAV: HTTP header, was: Issues from Interop/Inte rim WG Meeting
- Re: Interop issue: how can clients force authentication?
- Re: Interop issue: how can clients force authentication?
- WebDAV Meeting in Atlanta
- RE: extending the DAV: HTTP header, was: Issues from Interop/Inte rim WG Meeting
- RE: Interop issue: Can we require clients to accept cookies?
- RE: extending the DAV: HTTP header, was: Issues from Interop/Inte rim WG Meeting
- RE: Issue: Requiring server to use / terminated URL for returned collections
- RE: Issue: Requiring server to use / terminated URL for returned collections
- RE: Issue: Requiring server to use / terminated URL for returned collections
- RE: Issue: Requiring server to use / terminated URL for returned collections
- RE: ETags, was: Issues from Interop/Interim WG Meeting
- RE: extending the DAV: HTTP header, was: Issues from Interop/Inte rim WG Meeting
- RE: Issue: Requiring server to use / terminated URL for returned coll ections
- RE: Issue: Requiring server to use / terminated URL for returned collections
- Re: Interop issue: how can clients force authentication?
- ETags, was: Issues from Interop/Interim WG Meeting
- 302 in miultistattus, was: Issues from Interop/Interim WG Meeting
- extending the DAV: HTTP header, was: Issues from Interop/Interim WG Meeting
- Re: Interop issue: Can we require clients to accept cookies?
- Re: Issue: Requiring server to use / terminated URL for returned coll ections
- Re: Interop issue: how can clients force authentication?
Monday, 16 September 2002
- Re: Interop issue: Can we require clients to accept cookies?
- Interop issue: how can clients force authentication?
- RE: Interop issue: Proposal for fixing lock token provision
- RE: Issue: Requiring server to use / terminated URL for returned coll ections
- RE: Proposal: WebDAV and transactions
- RE: Proposal: WebDAV and transactions
- Issue: Requiring server to use / terminated URL for returned coll ections
- RE: Proposal: WebDAV and transactions
- RE: Interop issue: Can we require clients to accept cookies?
- Re: Interop issue: Can we require clients to accept cookies?
- Re: Interop issue: Can we require clients to accept cookies?
- Re: Interop issue: Can we require clients to accept cookies?
- Re: Interop issue: Can we require clients to accept cookies?
- RE: Notes for Sept 9 WG meeting (by Dennis Hamilton) - HTML Available
- Re: Interop issue: Proposal for fixing lock token provision
Sunday, 15 September 2002
- RE: Notes for Sept 9 WG meeting (by Dennis Hamilton) - HTML Available
- Notes for Sept 9 WG meeting (by Dennis Hamilton)
- Interop issue: Proposal for fixing lock token provision
- Interop issue: Can we require clients to accept cookies?
- Issues from Interop/Interim WG Meeting
Friday, 13 September 2002
- RE: Proposal: WebDAV and transactions - optional versioning usage
- RE: Proposal: WebDAV and transactions - stepping back to requirem ents
- Proposal: WebDAV and transactions - stepping back to requirements
- RE: Proposal: WebDAV and transactions - optional versioning usage
- Re: can a non-HTTP URL be the target of a redirect (301/302)
- Re: Proposal: WebDAV and transactions
- RE: Proposal: WebDAV and transactions
- Re: Proposal: WebDAV and transactions
Thursday, 12 September 2002
- RE: Proposal: WebDAV and transactions
- RE: Proposal: WebDAV and transactions
- Re: Proposal: WebDAV and transactions
- RE: Proposal: WebDAV and transactions
- RE: Proposal: WebDAV and transactions
- RE: Proposal: WebDAV and transactions
- RE: Proposal: WebDAV and transactions
- RE: Proposal: WebDAV and transactions
- RE: Proposal: WebDAV and transactions
- RE: Proposal: WebDAV and transactions
- RE: Proposal: WebDAV and transactions
- RE: Proposal: WebDAV and transactions
- can a non-HTTP URL be the target of a redirect (301/302)
- Re: Proposal: WebDAV and transactions
- Re: Proposal: WebDAV and transaction
- RE: Proposal: WebDAV and transactions
- DAV:resourceid
Thursday, 5 September 2002
Wednesday, 11 September 2002
- Re: FW: [Moderator Action] WEBDAV client on mainframe
- RE: Proposal: WebDAV and transactions
- Re: Proposal: WebDAV and transaction
- Re: Proposal: WebDAV and transactions
- RE: Proposal: WebDAV and transactions
- Re: Proposal: WebDAV and transactions
- RE: Proposal: WebDAV and transactions
- Re: Proposal: WebDAV and transactions
- Re: Proposal: WebDAV and transactions
- RE: Proposal: WebDAV and transactions
- Re: Proposal: WebDAV and transactions
- RE: best webDAV implementation
Tuesday, 10 September 2002
- Re: Proposal: WebDAV and transactions
- RE: Links to latest bis working docs
- RE: Links to latest bis working docs
- RE: Links to latest bis working docs
- RE: Links to latest bis working docs
- RE: Links to latest bis working docs
- RE: Links to latest bis working docs
- RE: Links to latest bis working docs
- RE: Links to latest bis working docs
- FW: best webDAV implementation
- FW: [Moderator Action] WEBDAV
- Links to latest bis working docs
Monday, 9 September 2002
- RE: Proposal: WebDAV and transactions
- RE: Proposal: WebDAV and transactions
- RE: Proposal: WebDAV and transactions
- RE: Proposal: WebDAV and transactions
- RE: Proposal: WebDAV and transactions
- RE: Proposal: WebDAV and transactions
- RE: Proposal: WebDAV and transactions
Sunday, 8 September 2002
Friday, 6 September 2002
- RE: What is left after LOCK/UNLOCK on null resource?
- RE: What is left after LOCK/UNLOCK on null resource?
- RE: Interoperability for DAV:ishidden?
Thursday, 5 September 2002
- Re: What is left after LOCK/UNLOCK on null resource?
- RE: Interoperability for DAV:ishidden?
- RE: What is left after LOCK/UNLOCK on null resource?
- RE: Interoperability for DAV:ishidden?
- Re: Interoperability for DAV:ishidden?
- RE: Interoperability for DAV:ishidden?
- Re: Interoperability for DAV:ishidden?
- RE: What is left after LOCK/UNLOCK on null resource?
- RE: What is left after LOCK/UNLOCK on null resource?
- Re: What is left after LOCK/UNLOCK on null resource?
- RE: Interoperability for DAV:ishidden?
- RE: Interoperability for DAV:ishidden?
- RE: Interoperability for DAV:ishidden?
- RE: Interoperability for DAV:ishidden?
- RE: Interoperability for DAV:ishidden?
- RE: What is left after LOCK/UNLOCK on null resource?
- RE: What is left after LOCK/UNLOCK on null resource?
- RE: Interoperability for DAV:ishidden?
- RE: What is left after LOCK/UNLOCK on null resource?
- RE: Interoperability for DAV:ishidden?
- RE: What is left after LOCK/UNLOCK on null resource?
- Re: Interoperability for DAV:ishidden?
- RE: What is left after LOCK/UNLOCK on null resource?
Wednesday, 4 September 2002
- Re: Interoperability for DAV:ishidden?
- Re: Interop Event FAQ
- Re: Interoperability for DAV:ishidden?
- Re: Interoperability for DAV:ishidden?
- RE: What is left after LOCK/UNLOCK on null resource?
- RE: Interoperability for DAV:ishidden?
- RE: What is left after LOCK/UNLOCK on null resource?
- Interoperability for DAV:ishidden?
- Re: What is left after LOCK/UNLOCK on null resource?
- What is left after LOCK/UNLOCK on null resource?
- Interop Event FAQ
Tuesday, 3 September 2002
Monday, 2 September 2002
- RE: Proposal: WebDAV and transactions
- RE: discovering the root of a deep lock
- RE: discovering the root of a deep lock
- Re: Proposal: WebDAV and transactions
- Proposal: WebDAV and transactions
Thursday, 29 August 2002
- Announcement of WebDAV WG Interim Meeting
- FW: [Moderator Action] WebDAV clients which work over Netscape Proxies?
Tuesday, 27 August 2002
Monday, 26 August 2002
Friday, 23 August 2002
Wednesday, 21 August 2002
Tuesday, 20 August 2002
- Re: IPv6 support in WebDAV and HTTP
- Re: IPv6 support in WebDAV and HTTP
- Re: IPv6 support in WebDAV and HTTP
- RE: IPv6 support in WebDAV and HTTP
- Re: IPv6 support in WebDAV and HTTP
- IPv6 support in WebDAV and HTTP
- RE: New RFC2518bis draft, COPY / MOVE of live properities
- RE: New RFC2518bis draft, COPY / MOVE of live properities
Monday, 19 August 2002
- Re: New RFC2518bis draft, COPY / MOVE of live properities
- RE: New RFC2518bis draft, COPY / MOVE of live properities
- Re: New RFC2518bis draft, COPY / MOVE of live properities
Thursday, 15 August 2002
Wednesday, 14 August 2002
Saturday, 10 August 2002
Friday, 9 August 2002
Thursday, 8 August 2002
Monday, 5 August 2002
- RE: PROPFIND vs REPORT vs depth infinity
- RE: PROPFIND vs REPORT vs depth infinity
- RE: PROPFIND vs REPORT vs depth infinity
- PROPFIND vs REPORT vs depth infinity
Sunday, 4 August 2002
Friday, 2 August 2002
- RE: New RFC2518bis draft, COPY / MOVE of live properities
- RE: New RFC2518bis draft, COPY / MOVE of live properities
- RE: Bindings
- RE: Bindings, was: Issue: URI_URL, proposed changes
- RE: New RFC2518bis draft, COPY / MOVE of live properities
- RE: Bindings
Thursday, 1 August 2002
- WebDAV Interoperability Event: New Dates
- Re: Bindings, was: Issue: URI_URL, proposed changes
- RE: New RFC2518bis draft, COPY / MOVE of live properities
- Bindings, was: Issue: URI_URL, proposed changes
Wednesday, 31 July 2002
- RE: New RFC2518bis draft, COPY / MOVE of live properities
- RE: Issue: URI_URL, proposed changes
- RE: Issue: URI_URL, proposed changes
- RE: Issue: URI_URL, proposed changes
- Re: Issue: URI_URL, proposed changes
- RE: Issue: URI_URL, proposed changes
- RE: Issue: URI_URL, proposed changes
- RE: Issue: URI_URL, proposed changes
- webdav and internet explorer
Tuesday, 30 July 2002
- Re: Web Character Model and IRI spec (Re: FW: character encoding.)
- I-D ACTION:draft-ietf-webdav-acl-09.txt
Monday, 29 July 2002
- Re: Mac OS X Client implementation issues
- Mac OS X Client implementation issues
- RE: Derived objects
- RE: Web Character Model and IRI spec (Re: FW: character encoding.)
Saturday, 27 July 2002
Friday, 26 July 2002
- Please review draft-ietf-webdav-acl-09
- Submitted -09 Access Control Protocol
- webDAV - macromedia dreamweaver ultradev - error trying to 'put' a file
Thursday, 25 July 2002
- RE: Doubt in error response
- RE: Open issues with internationalization section
- RE: New RFC2518bis draft, COPY / MOVE of live properities
- RE: New RFC2518bis draft, COPY / MOVE of live properities
- RE: New RFC2518bis draft, COPY / MOVE of live properities
- RE: New RFC2518bis draft, COPY / MOVE of live properities
- RE: New RFC2518bis draft, COPY / MOVE of live properities
- Re: Open issues with internationalization section
- RE: Open issues with internationalization section
- Re: Open issues with internationalization section
Wednesday, 24 July 2002
- Re: FW: 207 Multi-Status success
- FW: 207 Multi-Status success
- RE: Open issues with internationalization section
- RE: Issue: SOURCE_PROPERTY_UNDERSPECIFIED
- RE: Doubt in error response
- Open issues with internationalization section
- RE: New RFC2518bis draft, COPY / MOVE of live properities
- Re: If header simplification
- RE: New RFC2518bis draft, COPY / MOVE of live properities
- RE: New RFC2518bis draft, property values after LOCK of unmapped URL
- RE: New RFC2518bis draft, property values after LOCK of unmapped URL
- RE: New RFC2518bis draft, property values after LOCK of unmapped URL
- If header simplification
Tuesday, 23 July 2002
- RE: New RFC2518bis draft, property values after LOCK of unmapped URL
- RE: New RFC2518bis draft, property values after LOCK of unmapped URL
- RE: New RFC2518bis draft, COPY / MOVE of live properities
Monday, 22 July 2002
- RE: New RFC2518bis draft, property values after LOCK of unmapped URL
- RE: New RFC2518bis draft, property values after LOCK of unmapped URL
- issue: REMOVE_ETAG_SUPPORT_FOR_IF_HEADER
- FW: message board on webdav
- RE: New issue (?): locktoken (12.1.2) syntax
Saturday, 20 July 2002
- RE: Questions on Properties in RFC 2518
- RE: Questions on Properties in RFC 2518
- Questions on Properties in RFC 2518
Friday, 19 July 2002
- RE: [Moderator Action] Quick WebDAV Question for WebSphere Advisor Magazine
- RE: [Moderator Action] Quick WebDAV Question for WebSphere Advisor Magazine
- FW: [Moderator Action] Quick WebDAV Question for WebSphere Advisor Magazine
Thursday, 18 July 2002
Wednesday, 17 July 2002
Monday, 15 July 2002
Sunday, 14 July 2002
Saturday, 13 July 2002
- RE: Issue: URI_URL, proposed changes
- RE: Issue: URI_URL, proposed changes
- RE: Issue: URI_URL, proposed changes
- RE: Issue: URI_URL, proposed changes
Thursday, 11 July 2002
- WebDAV/DeltaV Face-to-Face Interoperability Testing Event
- RE: Issue: URI_URL, proposed changes
- RE: Issue: URI_URL, proposed changes
- RE: New issue (?): locktoken (12.1.2) syntax
- RE: New issue (?): locktoken (12.1.2) syntax
- Re: discovering the root of a deep lock, HOW_TO_FIND_THE_ROOT_OF_A_LOCK
- Re: New issue (?): locktoken (12.1.2) syntax
Wednesday, 10 July 2002
- RE: Issue: URI_URL, proposed changes
- Agenda for WebDAV WG meeting, Yokohama
- Re: discovering the root of a deep lock
- RE: discovering the root of a deep lock
- RE: discovering the root of a deep lock
- New issue (?): locktoken (12.1.2) syntax
- discovering the root of a deep lock
Tuesday, 9 July 2002
- RE: New RFC2518bis draft, MOVE vs COPY
- FW: character encoding.
- Re: A couple of issues
- A couple of issues
- response marshalling in RFC2518, section 8.10.10
- response marshalling in RFC2518, section 8.10.10
Monday, 8 July 2002
- Re: Issue: UNLOCK_WHAT_URL
- Re: Issue: UNLOCK_WHAT_URL
- RE: Issue: UNLOCK_WHAT_URL
- RE: Issue: UNLOCK_WHAT_URL
- RE: Issue: UNLOCK_WHAT_URL
- RE: New RFC2518bis draft, MOVE vs COPY
- Issue: UNLOCK_WHAT_URL
- RE: root of a lock, was HOW_TO_IDENTIFY_LOCK_OWNER
- RE: Tx of text type docs and CR/LF, CR, LF translation
- Re: New RFC2518bis draft
- RE: New RFC2518bis draft
- RE: root of a lock, was HOW_TO_IDENTIFY_LOCK_OWNER
- Re: root of a lock, was HOW_TO_IDENTIFY_LOCK_OWNER
- Re: New RFC2518bis draft
- RE: root of a lock, was HOW_TO_IDENTIFY_LOCK_OWNER
- RE: root of a lock, was HOW_TO_IDENTIFY_LOCK_OWNER
- RE: New RFC2518bis draft
Sunday, 7 July 2002
Saturday, 6 July 2002
- RE: New RFC2518bis draft
- RE: Issue: SOURCE_PROPERTY_UNDERSPECIFIED
- RE: New RFC2518bis draft, xml:lang
Thursday, 4 July 2002
- Doubt in error response
- RE: Problem in Frontpage
- RE: New RFC2518bis draft
- RE: Problem in Frontpage
- Problem in Frontpage
Wednesday, 3 July 2002
- Re: Q?: Tx of text type docs and CR/LF, CR, LF translation
- RE: New RFC2518bis draft
- RE: Tx of text type docs and CR/LF, CR, LF translation
- RE: I-D ACTION:draft-mealling-iana-xmlns-registry-04.txt
- RE: I-D ACTION:draft-mealling-iana-xmlns-registry-04.txt
- Q?: Tx of text type docs and CR/LF, CR, LF translation
- RE: I-D ACTION:draft-mealling-iana-xmlns-registry-04.txt
- FW: WebDav information
- FW: I-D ACTION:draft-mealling-iana-xmlns-registry-04.txt
Tuesday, 2 July 2002
- RE: Issue: SOURCE_PROPERTY_UNDERSPECIFIED
- Re: New RFC2518bis draft, LOCK_REFRESH_BY_METHODS
- RE: Issue: SOURCE_PROPERTY_UNDERSPECIFIED
- Re: java, server-side lock/unlock resource - simple example?
- java, server-side lock/unlock resource - simple example?
- I-D ACTION:draft-ietf-webdav-rfc2518bis-01.txt