w3c-dist-auth@w3.org from January to March 2006 by date

Friday, 31 March 2006

• feedback on rfc2518bis-14: locking Manfred Baedke

Tuesday, 28 March 2006

• Re: Next steps -- WG last call issues on RFC2518bis Julian Reschke
• Next steps -- WG last call issues on RFC2518bis Lisa Dusseault

Thursday, 23 March 2006

• Re: Comments on the "new" 2518 -- XSS Jason Crawford

Wednesday, 22 March 2006

• Re: rfc2518bis-14: the term 'DAV-compliance' Manfred Baedke
• Re: rfc2518bis-14: the term 'DAV-compliance' Wilfredo Sánchez Vega
• Re: Atomic MOVE vs BIND spec, was: Comments on the "new" 2518 Jim Luther
• Re: Comments on the "new" 2518 -- XSS Julian Reschke
• Re: Comments on the "new" 2518 -- XSS Jason Crawford

Tuesday, 21 March 2006

• Re: Atomic MOVE vs BIND spec, was: Comments on the "new" 2518 Julian Reschke
• Re: Comments on the "new" 2518 -- XSS Julian Reschke

Monday, 20 March 2006

• Re: Comments on the "new" 2518--Display Name Elias Sinderson
• RE: Comments on the "new" 2518--Display Name John Barone
• Re: Comments on the "new" 2518--Display Name Jason Crawford
• Re: Comments on the "new" 2518--Display Name Julian Reschke
• Re: DIFF method Werner Donné
• Re: DIFF method Geoffrey M Clemm
• Re: DIFF method Werner Donné
• Re: DIFF method Geoffrey M Clemm
• rfc3253: DIFF method Werner Donné
• Re: Comments on the "new" 2518--Display Name Geoffrey M Clemm

Sunday, 19 March 2006

• Re: Comments on the "new" 2518--Display Name Jason Crawford
• Re: Comments on the "new" 2518--Display Name Julian Reschke

Saturday, 18 March 2006

• Re: [Ietf-caldav] Re: CalDAV draft Informal Last-Call Julian Reschke

Friday, 17 March 2006

• Re: UPDATE method and forking Geoffrey M Clemm
• Re: UPDATE method and forking Manfred Baedke
• Re: UPDATE method and forking Geoffrey M Clemm
• Re: UPDATE method and forking Manfred Baedke
• Re: UPDATE method and forking Geoffrey M Clemm
• Re: UPDATE method and forking Geoffrey M Clemm
• Re: UPDATE method and forking Werner Donné
• Re: UPDATE method and forking Werner Donné
• Re: UPDATE method and forking Geoffrey M Clemm
• Re: UPDATE method and forking Manfred Baedke
• Re: rfc2518bis-14: locking terminology Manfred Baedke
• Re: UPDATE method and forking Werner Donné

Thursday, 16 March 2006

• RE: rfc2518bis-14: locking terminology John Barone
• Re: UPDATE method and forking Manfred Baedke
• Re: rfc2518bis-14: locking terminology Manfred Baedke
• Re: UPDATE method and forking Werner Donné
• RE: rfc2518bis-14: locking terminology John Barone
• Re: rfc2518bis-14: locking terminology Manfred Baedke
• RE: rfc2518bis-14: locking terminology John Barone
• Re: UPDATE method and forking Geoffrey M Clemm
• Re: rfc2518bis-14: COPY/MOVE semantics Julian Reschke
• Re: UPDATE method and forking Werner Donné
• Re: UPDATE method and forking Geoffrey M Clemm
• Re: UPDATE method and forking Werner Donné
• Re: rfc2518bis-14: locking terminology Geoffrey M Clemm
• Re: [Ietf-caldav] Re: CalDAV draft Informal Last-Call Bernard Desruisseaux

Wednesday, 15 March 2006

• rfc2518bis-14: locking terminology Manfred Baedke
• RE: rfc2518bis-14: COPY/MOVE semantics John Barone
• Re: Atomic MOVE vs BIND spec, was: Comments on the "new" 2518 Jim Luther
• Re: UPDATE method and forking Geoffrey M Clemm
• Re: rfc2518bis-14: COPY/MOVE semantics Manfred Baedke
• Re: rfc2518bis-14: COPY/MOVE semantics Julian Reschke
• RE: rfc2518bis-14 WGLC comments (part 1) John Barone
• RE: rfc2518bis-14: COPY/MOVE semantics John Barone
• RE: Atomic MOVE vs BIND spec, was: Comments on the "new" 2518 John Barone
• Re: rfc2518bis-14 WGLC comments (part 2) Julian Reschke
• rfc2518bis-14 WGLC comments (part 1) Julian Reschke
• rfc2518bis-14: the term 'DAV-compliance' Manfred Baedke
• rfc2518bis-14: COPY/MOVE semantics Manfred Baedke
• Re: UPDATE method and forking Werner Donné
• Re: UPDATE method and forking Geoffrey M Clemm
• UPDATE method and forking Werner Donné

Tuesday, 14 March 2006

• Re: Comments on the "new" 2518 Manfred Baedke
• Atomic MOVE vs BIND spec, was: Comments on the "new" 2518 Julian Reschke
• RE: Comments on the "new" 2518 John Barone
• feedback on rfc2518bis-14 Manfred Baedke

Monday, 13 March 2006

• Re: Comments on the "new" 2518 Julian Reschke
• Re: folder view in frames Joe Feise
• RE: Comments on the "new" 2518 John Barone
• Re: folder view in frames Julian Reschke
• Re: Comments on the "new" 2518 Julian Reschke
• RE: Issue 202, Lock-Null resources John Barone
• RE: Comments on the "new" 2518 John Barone
• folder view in frames Praehauser Julia
• Re: Issue 181, DAV:error Geoffrey M Clemm

Sunday, 12 March 2006

• Re: Issue 202, Lock-Null resources Geoffrey M Clemm
• Issue 202, Lock-Null resources Julian Reschke
• Issue 181, DAV:error Julian Reschke
• Re: WGLC of draft-ietf-webdav-rfc2518bis-14.txt Julian Reschke

Saturday, 11 March 2006

• Issue 177 (status descriptions) Julian Reschke

Thursday, 9 March 2006

• RE: Comments on the "new" 2518 Geoffrey M Clemm
• RE: Comments on the "new" 2518 John Barone
• [Bug 230] tagged lists and repeating URIs bugzilla@soe.ucsc.edu

Tuesday, 7 March 2006

• Re: CalDAV draft Informal Last-Call Bernard Desruisseaux
• Re: Comments on the "new" 2518 Julian Reschke
• Re: Comments on the "new" 2518 Geoffrey M Clemm
• Re: Comments on the "new" 2518 Lisa Dusseault

Monday, 6 March 2006

• Re: Comments on the "new" 2518 Julian Reschke
• Re: Comments on the "new" 2518 Lisa Dusseault
• RE: Comments on the "new" 2518 Geoffrey M Clemm
• RE: Comments on the "new" 2518 John Barone
• Re: Comments on the "new" 2518--Display Name Geoffrey M Clemm
• Re: Comments on the "new" 2518--Display Name Julian Reschke

Friday, 3 March 2006

• RE: Comments on the "new" 2518--Display Name Kevin Wiggen
• RE: Comments on the "new" 2518 -- XSS Kevin Wiggen
• Re: Comments on the "new" 2518--Display Name Julian Reschke

Thursday, 2 March 2006

• Comments on the 2518 Alex Jalali
• RE: I-D ACTION:draft-whitehead-http-etag-00.txt Larry Masinter
• RE: Comments on the "new" 2518--Display Name Kevin Wiggen
• Re: Comments on the "new" 2518--Display Name Julian Reschke
• RE: Comments on the "new" 2518--Display Name Kevin Wiggen
• Re: Comments on the "new" 2518 -- XSS Julian Reschke
• Re: Comments on the "new" 2518 -- Compliance Level Julian Reschke
• Re: Comments on the "new" 2518-- Dav Namespace Julian Reschke
• Re: Comments on the "new" 2518 Julian Reschke
• Re: Comments on the "new" 2518 Julian Reschke
• Re: I-D ACTION:draft-whitehead-http-etag-00.txt Julian Reschke
• Re: Comments on the "new" 2518 Geoffrey M Clemm
• Re: Comments on the "new" 2518 Geoffrey M Clemm
• Comments on the "new" 2518 -- XSS Kevin Wiggen
• Comments on the "new" 2518 -- Compliance Level Kevin Wiggen
• Comments on the "new" 2518-- Dav Namespace Kevin Wiggen
• Comments on the "new" 2518 Kevin Wiggen
• Comments on the "new" 2518 Kevin Wiggen
• Comments on the "new" 2518 Kevin Wiggen

Tuesday, 28 February 2006

• Re: Webdav (apache) not enforcing limits Wilfredo Sánchez Vega
• Webdav (apache) not enforcing limits Sean Davis

Sunday, 26 February 2006

• Bug 143 (lock refresh), was: WGLC of draft-ietf-webdav-rfc2518bis-14.txt Julian Reschke
• Re: 2518bis-14 feedback Julian Reschke

Friday, 24 February 2006

• 2518bis-14 feedback Joe Orton
• Re: I-D ACTION:draft-ietf-webdav-bind-14.txt Julian Reschke
• [Fwd: I-D ACTION:draft-dusseault-caldav-10.txt] Bernard Desruisseaux

Thursday, 23 February 2006

• I-D ACTION:draft-ietf-webdav-bind-14.txt Internet-Drafts@ietf.org
• Re: CalDAV draft Informal Last-Call Julian Reschke
• Re: CalDAV draft Informal Last-Call Bernard Desruisseaux
• Re: WGLC of draft-ietf-webdav-rfc2518bis-14.txt Stefan Eissing
• Re: CalDAV draft Informal Last-Call Julian Reschke
• CalDAV draft Informal Last-Call Bernard Desruisseaux

Wednesday, 22 February 2006

• WGLC of draft-ietf-webdav-rfc2518bis-14.txt Cullen Jennings
• Re: Possible problem in collection definition Julian Reschke

Tuesday, 21 February 2006

• I-D ACTION:draft-ietf-webdav-rfc2518bis-14.txt Internet-Drafts@ietf.org
• Re: Possible problem in collection definition Wilfredo Sánchez Vega
• Re: Possible problem in collection definition Lisa Dusseault
• Re: Possible problem in collection definition Julian Reschke

Monday, 20 February 2006

• Re: Possible problem in collection definition Wilfredo Sánchez Vega
• [Bug 188] PROPFIND include-dead-props bugzilla@soe.ucsc.edu
• [Bug 188] PROPFIND include-dead-props bugzilla@soe.ucsc.edu
• Re: Fw: Possible problem in collection definition Julian Reschke
• Re: Fw: Possible problem in collection definition Elias Sinderson
• Re: Fw: Possible problem in collection definition Elias Sinderson
• Lock refresh (If header vs Lock-Token header) Julian Reschke
• Re: Fw: Possible problem in collection definition Julian Reschke
• Re: Fw: Possible problem in collection definition Geoffrey M Clemm
• [Bug 233] Text organization in "LOCK Method" bugzilla@soe.ucsc.edu
• [Bug 233] New: Text organization in "LOCK Method" bugzilla@soe.ucsc.edu
• Re: Fw: Possible problem in collection definition Julian Reschke

Sunday, 19 February 2006

• Re: Fw: Possible problem in collection definition Albert Lunde
• Re: Fw: Possible problem in collection definition Jason Crawford
• Re: Possible problem in collection definition Lisa Dusseault
• Re: Possible problem in collection definition Jason Crawford
• Re: Possible problem in collection definition Lisa Dusseault
• Fw: Possible problem in collection definition Geoffrey M Clemm

Saturday, 18 February 2006

• Re: Possible problem in collection definition Geoffrey M Clemm
• Re: Possible problem in collection definition Jason Crawford
• Re: Possible problem in collection definition Geoffrey M Clemm
• Last Call of 2518bis to happen REAL SOON NOW ... Cullen Jennings

Friday, 17 February 2006

• [Bug 13] new ETag requirements bugzilla@soe.ucsc.edu
• [Bug 13] new ETag requirements bugzilla@soe.ucsc.edu
• [Bug 208] spec contradictory in ETag requirements bugzilla@soe.ucsc.edu
• [Bug 18] no record of consensus for force-authenticate bugzilla@soe.ucsc.edu
• [Bug 161] If header section rewrite (was: EVALUATE_ALL_OF_IF_HEADER) bugzilla@soe.ucsc.edu
• [Bug 144] IF_HEADER_CHECKS_AFTER_OTHER_CHECKS bugzilla@soe.ucsc.edu
• [Bug 161] If header section rewrite (was: EVALUATE_ALL_OF_IF_HEADER) bugzilla@soe.ucsc.edu
• Re: Possible problem in collection definition Julian Reschke
• Re: Possible problem in collection definition Jason Crawford
• [Bug 73] "Changes" section missing bugzilla@soe.ucsc.edu
• [Bug 161] If header section rewrite (was: EVALUATE_ALL_OF_IF_HEADER) bugzilla@soe.ucsc.edu
• [Bug 227] Collection state definition in conflict between BIND and RFC2518bis bugzilla@soe.ucsc.edu
• Re: Possible problem in collection definition Julian Reschke
• Possible problem in collection definition Lisa Dusseault
• [Bug 161] If header section rewrite (was: EVALUATE_ALL_OF_IF_HEADER) bugzilla@soe.ucsc.edu

Thursday, 16 February 2006

• [Bug 73] "Changes" section missing bugzilla@soe.ucsc.edu
• [Bug 227] Collection state definition in conflict between BIND and RFC2518bis bugzilla@soe.ucsc.edu
• [Bug 227] Collection state definition in conflict between BIND and RFC2518bis bugzilla@soe.ucsc.edu

Wednesday, 15 February 2006

• [Bug 161] If header section rewrite (was: EVALUATE_ALL_OF_IF_HEADER) bugzilla@soe.ucsc.edu
• [Bug 161] If header section rewrite (was: EVALUATE_ALL_OF_IF_HEADER) bugzilla@soe.ucsc.edu
• [Bug 144] IF_HEADER_CHECKS_AFTER_OTHER_CHECKS bugzilla@soe.ucsc.edu
• [Bug 161] If header section rewrite (was: EVALUATE_ALL_OF_IF_HEADER) bugzilla@soe.ucsc.edu
• [Bug 18] no record of consensus for force-authenticate bugzilla@soe.ucsc.edu
• [Bug 144] IF_HEADER_CHECKS_AFTER_OTHER_CHECKS bugzilla@soe.ucsc.edu
• [Bug 143] LOCK_RENEWAL_SHOULD_NOT_USE_IF_HEADER bugzilla@soe.ucsc.edu
• [Bug 230] tagged lists and repeating URIs bugzilla@soe.ucsc.edu
• [Bug 73] "Changes" section missing bugzilla@soe.ucsc.edu
• [Bug 232] Section organization for XML marshalling bugzilla@soe.ucsc.edu
• [Bug 232] Section organization for XML marshalling bugzilla@soe.ucsc.edu
• [Bug 202] Move description of lock-null resources into appendix bugzilla@soe.ucsc.edu
• [Bug 100] "Notes on HTTP Client Compatibility" useful? bugzilla@soe.ucsc.edu
• [Bug 100] "Notes on HTTP Client Compatibility" useful? bugzilla@soe.ucsc.edu
• [Bug 177] "PROPFIND status codes" section bugzilla@soe.ucsc.edu
• [Bug 195] LOCK_ISSUES_WRITE_LOCKS_AND_COPYMOVE bugzilla@soe.ucsc.edu
• [Bug 217] GULP integration bugzilla@soe.ucsc.edu
• [Bug 229] GULP / Lock timeout discussion bugzilla@soe.ucsc.edu
• [Bug 143] LOCK_RENEWAL_SHOULD_NOT_USE_IF_HEADER bugzilla@soe.ucsc.edu
• [Bug 230] tagged lists and repeating URIs bugzilla@soe.ucsc.edu
• [Bug 227] Collection state definition in conflict between BIND and RFC2518bis bugzilla@soe.ucsc.edu
• [Bug 227] Collection state definition in conflict between BIND and RFC2518bis bugzilla@soe.ucsc.edu
• [Bug 13] new ETag requirements bugzilla@soe.ucsc.edu
• [Bug 161] EVALUATE_ALL_OF_IF_HEADER bugzilla@soe.ucsc.edu
• [Bug 161] EVALUATE_ALL_OF_IF_HEADER bugzilla@soe.ucsc.edu
• [Bug 73] "Changes" section missing bugzilla@soe.ucsc.edu
• Section 5.2 of draft-ietf-webdav-rfc2518bis-13 still has problems Geoffrey M Clemm
• [Bug 100] "Notes on HTTP Client Compatibility" useful? bugzilla@soe.ucsc.edu

Tuesday, 14 February 2006

• I-D ACTION:draft-ietf-webdav-rfc2518bis-13.txt Internet-Drafts@ietf.org
• [Bug 227] Collection state definition in conflict between BIND and RFC2518bis bugzilla@soe.ucsc.edu
• [Bug 143] LOCK_RENEWAL_SHOULD_NOT_USE_IF_HEADER bugzilla@soe.ucsc.edu
• [Bug 229] GULP / Lock timeout discussion bugzilla@soe.ucsc.edu
• Recent draft on Web publishing and editing Lisa Dusseault

Monday, 13 February 2006

• [Bug 13] new ETag requirements bugzilla@soe.ucsc.edu
• [Bug 208] spec contradictory in ETag requirements bugzilla@soe.ucsc.edu

Sunday, 12 February 2006

• [Bug 73] "Changes" section missing bugzilla@soe.ucsc.edu
• [Bug 73] "Changes" section missing bugzilla@soe.ucsc.edu
• [Bug 232] New: Section organization for XML marshalling bugzilla@soe.ucsc.edu
• [Bug 231] New: Rename "Coded-URL" production to "Coded-URI" bugzilla@soe.ucsc.edu

Saturday, 11 February 2006

• [Bug 73] "Changes" section missing bugzilla@soe.ucsc.edu
• [Bug 73] "Changes" section missing bugzilla@soe.ucsc.edu
• [Bug 230] tagged lists and repeating URIs bugzilla@soe.ucsc.edu
• [Bug 161] EVALUATE_ALL_OF_IF_HEADER bugzilla@soe.ucsc.edu
• [Bug 161] EVALUATE_ALL_OF_IF_HEADER bugzilla@soe.ucsc.edu
• [Bug 161] EVALUATE_ALL_OF_IF_HEADER bugzilla@soe.ucsc.edu
• [Bug 230] tagged lists and repeating URIs bugzilla@soe.ucsc.edu
• [Bug 161] EVALUATE_ALL_OF_IF_HEADER bugzilla@soe.ucsc.edu
• [Bug 230] New: tagged lists and repeating URIs bugzilla@soe.ucsc.edu
• [Bug 229] GULP / Lock timeout discussion bugzilla@soe.ucsc.edu
• [Bug 213] Spec inconsistent on PROPFIND/Depth:infinity bugzilla@soe.ucsc.edu
• [Bug 211] Inconsistencies about Destination header bugzilla@soe.ucsc.edu
• [Bug 227] Collection state definition in conflict between BIND and RFC2518bis bugzilla@soe.ucsc.edu
• [Bug 229] GULP / Lock timeout discussion bugzilla@soe.ucsc.edu
• [Bug 227] Collection state definition in conflict between BIND and RFC2518bis bugzilla@soe.ucsc.edu
• [Bug 181] error element bugzilla@soe.ucsc.edu
• [Bug 220] Do status codes belong into pre/postcondition definitions? bugzilla@soe.ucsc.edu
• [Bug 213] Spec inconsistent on PROPFIND/Depth:infinity bugzilla@soe.ucsc.edu
• [Bug 211] Inconsistencies about Destination header bugzilla@soe.ucsc.edu
• [Bug 152] SHOULD_A_SERVER_DETERMINE_MIMETYPE_OF_CONTENT bugzilla@soe.ucsc.edu

Friday, 10 February 2006

• [Bug 217] GULP integration bugzilla@soe.ucsc.edu
• [Bug 18] no record of consensus for force-authenticate bugzilla@soe.ucsc.edu
• [Bug 144] IF_HEADER_CHECKS_AFTER_OTHER_CHECKS bugzilla@soe.ucsc.edu
• [Bug 100] "Notes on HTTP Client Compatibility" useful? bugzilla@soe.ucsc.edu
• [Bug 217] GULP integration bugzilla@soe.ucsc.edu
• [Bug 46] URLs in Multistatus bugzilla@soe.ucsc.edu
• [Bug 217] GULP integration bugzilla@soe.ucsc.edu
• Re: I-D ACTION:draft-ietf-webdav-bind-13.txt Julian Reschke
• I-D ACTION:draft-ietf-webdav-bind-13.txt Internet-Drafts@ietf.org
• [Bug 72] Review references section bugzilla@soe.ucsc.edu
• [Bug 72] Review references section bugzilla@soe.ucsc.edu
• [Bug 72] Review references section bugzilla@soe.ucsc.edu
• [Bug 72] Review references section bugzilla@soe.ucsc.edu
• [Bug 217] GULP integration bugzilla@soe.ucsc.edu
• [Bug 217] GULP integration bugzilla@soe.ucsc.edu
• [Bug 161] EVALUATE_ALL_OF_IF_HEADER bugzilla@soe.ucsc.edu
• [Bug 220] Do status codes belong into pre/postcondition definitions? bugzilla@soe.ucsc.edu
• [Bug 229] GULP / Lock timeout discussion bugzilla@soe.ucsc.edu
• [Bug 229] GULP / Lock timeout discussion bugzilla@soe.ucsc.edu
• [Bug 181] error element bugzilla@soe.ucsc.edu
• [Bug 188] PROPFIND include-dead-props bugzilla@soe.ucsc.edu
• [Bug 181] error element bugzilla@soe.ucsc.edu
• [Bug 226] if matching and non-existant resources bugzilla@soe.ucsc.edu
• [Bug 161] EVALUATE_ALL_OF_IF_HEADER bugzilla@soe.ucsc.edu
• [Bug 181] error element bugzilla@soe.ucsc.edu
• [Bug 223] Section organization for pre/postconditions bugzilla@soe.ucsc.edu
• [Bug 222] Remove DTD fragments from pre/postcondition definitions when EMPTY bugzilla@soe.ucsc.edu
• [Bug 181] error element bugzilla@soe.ucsc.edu
• [Bug 221] condition code for write access to protected properties bugzilla@soe.ucsc.edu
• [Bug 221] condition code for write access to protected properties bugzilla@soe.ucsc.edu
• [Bug 220] Do status codes belong into pre/postcondition definitions? bugzilla@soe.ucsc.edu
• [Bug 220] Do status codes belong into pre/postcondition definitions? bugzilla@soe.ucsc.edu
• [Bug 220] Do status codes belong into pre/postcondition definitions? bugzilla@soe.ucsc.edu
• [Bug 161] EVALUATE_ALL_OF_IF_HEADER bugzilla@soe.ucsc.edu

Thursday, 9 February 2006

• [Bug 229] GULP / Lock timeout discussion bugzilla@soe.ucsc.edu
• [Bug 229] GULP / Lock timeout discussion bugzilla@soe.ucsc.edu
• [Bug 229] GULP / Lock timeout discussion bugzilla@soe.ucsc.edu
• [Bug 217] GULP integration bugzilla@soe.ucsc.edu
• [Bug 229] New: GULP / Lock timeout discussion bugzilla@soe.ucsc.edu
• [Bug 221] condition code for write access to protected properties bugzilla@soe.ucsc.edu
• [Bug 221] condition code for write access to protected properties bugzilla@soe.ucsc.edu
• [Bug 181] error element bugzilla@soe.ucsc.edu

Wednesday, 8 February 2006

• [Bug 217] GULP integration bugzilla@soe.ucsc.edu
• [Bug 217] GULP integration bugzilla@soe.ucsc.edu
• [Bug 217] GULP integration bugzilla@soe.ucsc.edu
• [Bug 202] Move description of lock-null resources into appendix bugzilla@soe.ucsc.edu
• [Bug 202] Move description of lock-null resources into appendix bugzilla@soe.ucsc.edu
• [Bug 202] Move description of lock-null resources into appendix bugzilla@soe.ucsc.edu
• [Bug 73] "Changes" section missing bugzilla@soe.ucsc.edu
• [Bug 195] LOCK_ISSUES_WRITE_LOCKS_AND_COPYMOVE bugzilla@soe.ucsc.edu
• [Bug 217] GULP integration bugzilla@soe.ucsc.edu
• [Bug 217] GULP integration bugzilla@soe.ucsc.edu
• [Bug 152] SHOULD_A_SERVER_DETERMINE_MIMETYPE_OF_CONTENT bugzilla@soe.ucsc.edu
• [Bug 152] SHOULD_A_SERVER_DETERMINE_MIMETYPE_OF_CONTENT bugzilla@soe.ucsc.edu
• [Bug 100] "Notes on HTTP Client Compatibility" useful? bugzilla@soe.ucsc.edu
• [Bug 144] IF_HEADER_CHECKS_AFTER_OTHER_CHECKS bugzilla@soe.ucsc.edu
• [Bug 227] Collection state definition in conflict between BIND and RFC2518bis bugzilla@soe.ucsc.edu
• [Bug 213] Spec inconsistent on PROPFIND/Depth:infinity bugzilla@soe.ucsc.edu
• [Bug 211] Inconsistencies about Destination header bugzilla@soe.ucsc.edu
• [Bug 100] "Notes on HTTP Client Compatibility" useful? bugzilla@soe.ucsc.edu
• [Bug 46] URLs in Multistatus bugzilla@soe.ucsc.edu
• [Bug 100] "Notes on HTTP Client Compatibility" useful? bugzilla@soe.ucsc.edu
• [Bug 46] URLs in Multistatus bugzilla@soe.ucsc.edu
• [Bug 227] Collection state definition in conflict between BIND and RFC2518bis bugzilla@soe.ucsc.edu
• [Bug 213] Spec inconsistent on PROPFIND/Depth:infinity bugzilla@soe.ucsc.edu
• [Bug 211] Inconsistencies about Destination header bugzilla@soe.ucsc.edu
• [Bug 73] "Changes" section missing bugzilla@soe.ucsc.edu
• [Bug 73] "Changes" section missing bugzilla@soe.ucsc.edu

Tuesday, 7 February 2006

• [Bug 161] EVALUATE_ALL_OF_IF_HEADER bugzilla@soe.ucsc.edu
• [Bug 144] IF_HEADER_CHECKS_AFTER_OTHER_CHECKS bugzilla@soe.ucsc.edu
• [Bug 18] no record of consensus for force-authenticate bugzilla@soe.ucsc.edu
• [Bug 228] If header weak etag matching bugzilla@soe.ucsc.edu
• [Bug 227] Collection state definition in conflict between BIND and RFC2518bis bugzilla@soe.ucsc.edu

Monday, 6 February 2006

• I-D ACTION:draft-ietf-webdav-rfc2518bis-12.txt Internet-Drafts@ietf.org
• [Bug 73] "Changes" section missing bugzilla@soe.ucsc.edu

Sunday, 5 February 2006

• [Bug 217] GULP integration bugzilla@soe.ucsc.edu

Saturday, 4 February 2006

• [Bug 213] Spec inconsistent on PROPFIND/Depth:infinity bugzilla@soe.ucsc.edu
• Re: BugZilla issue 213, PROPFIND:infinity Wilfredo Sánchez Vega
• [Bug 211] Inconsistencies about Destination header bugzilla@soe.ucsc.edu
• [Bug 46] URLs in Multistatus bugzilla@soe.ucsc.edu
• [Bug 46] URLs in Multistatus bugzilla@soe.ucsc.edu
• [Bug 152] SHOULD_A_SERVER_DETERMINE_MIMETYPE_OF_CONTENT bugzilla@soe.ucsc.edu
• Re: BugZilla issue 213, PROPFIND:infinity Julian Reschke
• Re: BugZilla issue 213, PROPFIND:infinity Julian Reschke
• [Bug 213] Spec inconsistent on PROPFIND/Depth:infinity bugzilla@soe.ucsc.edu
• Re: BugZilla issue 213, PROPFIND:infinity Wilfredo Sánchez Vega

Friday, 3 February 2006

• Re: BugZilla issue 213, PROPFIND:infinity Lisa Dusseault
• BugZilla issue 213, PROPFIND:infinity Julian Reschke
• [Bug 213] Spec inconsistent on PROPFIND/Depth:infinity bugzilla@soe.ucsc.edu
• [Bug 228] If header weak etag matching bugzilla@soe.ucsc.edu
• [Bug 152] SHOULD_A_SERVER_DETERMINE_MIMETYPE_OF_CONTENT bugzilla@soe.ucsc.edu
• [Bug 152] SHOULD_A_SERVER_DETERMINE_MIMETYPE_OF_CONTENT bugzilla@soe.ucsc.edu
• [Bug 73] "Changes" section missing bugzilla@soe.ucsc.edu
• [Bug 72] Review references section bugzilla@soe.ucsc.edu
• [Bug 46] URLs in Multistatus bugzilla@soe.ucsc.edu
• [Bug 208] spec contradictory in ETag requirements bugzilla@soe.ucsc.edu
• [Bug 13] new ETag requirements bugzilla@soe.ucsc.edu
• [Bug 35] RFC2606 compliance bugzilla@soe.ucsc.edu
• [Bug 228] If header weak etag matching bugzilla@soe.ucsc.edu
• [Bug 224] add example for URI escaping in DAV:href bugzilla@soe.ucsc.edu
• [Bug 46] URLs in Multistatus bugzilla@soe.ucsc.edu
• [Bug 152] SHOULD_A_SERVER_DETERMINE_MIMETYPE_OF_CONTENT bugzilla@soe.ucsc.edu
• [Bug 217] GULP integration bugzilla@soe.ucsc.edu

Thursday, 2 February 2006

• [Bug 227] Collection state definition in conflict between BIND and RFC2518bis bugzilla@soe.ucsc.edu
• [Bug 227] Collection state definition in conflict between BIND and RFC2518bis bugzilla@soe.ucsc.edu
• [Bug 228] New: If header weak etag matching bugzilla@soe.ucsc.edu
• Re: change notifications Cullen Jennings

Wednesday, 1 February 2006

• Document organization around Changes section Cullen Jennings
• [Bug 179] DAV:no-lock bugzilla@soe.ucsc.edu
• [Bug 161] EVALUATE_ALL_OF_IF_HEADER bugzilla@soe.ucsc.edu
• [Bug 161] EVALUATE_ALL_OF_IF_HEADER bugzilla@soe.ucsc.edu
• [Bug 46] URLs in Multistatus bugzilla@soe.ucsc.edu
• [Bug 46] URLs in Multistatus bugzilla@soe.ucsc.edu
• Re: [Bug 226] if matching and non-existant resources Julian Reschke
• Re: change notifications Joachim Feise
• Re: [Bug 226] if matching and non-existant resources Elias Sinderson

Tuesday, 31 January 2006

• Re: [Bug 227] Collection state definition in conflict between BIND and RFC2518bis Julian Reschke
• [Bug 227] Collection state definition in conflict between BIND and RFC2518bis bugzilla@soe.ucsc.edu
• [Bug 227] Collection state definition in conflict between BIND and RFC2518bis bugzilla@soe.ucsc.edu
• Re: change notifications Jim Luther
• change notifications Stefan Eissing
• [Bug 35] RFC2606 compliance bugzilla@soe.ucsc.edu
• [Bug 213] Spec inconsistent on PROPFIND/Depth:infinity bugzilla@soe.ucsc.edu
• [Bug 217] GULP integration bugzilla@soe.ucsc.edu

Monday, 30 January 2006

• [Bug 217] GULP integration bugzilla@soe.ucsc.edu
• [Bug 213] Spec inconsistent on PROPFIND/Depth:infinity bugzilla@soe.ucsc.edu
• [Bug 188] PROPFIND include-dead-props bugzilla@soe.ucsc.edu
• [Bug 152] SHOULD_A_SERVER_DETERMINE_MIMETYPE_OF_CONTENT bugzilla@soe.ucsc.edu
• Re: Relative references and whether requires an authority Julian Reschke
• [Bug 179] DAV:no-lock bugzilla@soe.ucsc.edu
• Re: Relative references and whether requires an authority Lisa Dusseault
• [Bug 217] GULP integration bugzilla@soe.ucsc.edu
• [Bug 213] Spec inconsistent on PROPFIND/Depth:infinity bugzilla@soe.ucsc.edu
• [Bug 181] error element bugzilla@soe.ucsc.edu
• [Bug 221] condition code for write access to protected properties bugzilla@soe.ucsc.edu
• [Bug 219] mixed content in DAV:error bugzilla@soe.ucsc.edu
• [Bug 217] GULP integration bugzilla@soe.ucsc.edu
• [Bug 211] Inconsistencies about Destination header bugzilla@soe.ucsc.edu
• [Bug 213] Spec inconsistent on PROPFIND/Depth:infinity bugzilla@soe.ucsc.edu
• [Bug 211] Inconsistencies about Destination header bugzilla@soe.ucsc.edu
• [Bug 210] incorrect statement on PROPPATCH and property recurrence bugzilla@soe.ucsc.edu
• [Bug 188] PROPFIND include-dead-props bugzilla@soe.ucsc.edu
• [Bug 184] Clarifications requested for section 19.8 on hosting malicious content bugzilla@soe.ucsc.edu
• [Bug 179] DAV:no-lock bugzilla@soe.ucsc.edu
• [Bug 152] SHOULD_A_SERVER_DETERMINE_MIMETYPE_OF_CONTENT bugzilla@soe.ucsc.edu
• [Bug 53] DAV:responsedescription content model bugzilla@soe.ucsc.edu
• Re: Relative references and whether requires an authority Lisa Dusseault
• [Bug 46] URLs in Multistatus bugzilla@soe.ucsc.edu
• [Bug 35] RFC2606 compliance bugzilla@soe.ucsc.edu
• [Bug 227] Collection state definition in conflict between BIND and RFC2518bis bugzilla@soe.ucsc.edu
• [Bug 227] New: Collection state definition in conflict between BIND and RFC2518bis bugzilla@soe.ucsc.edu
• [Bug 217] GULP integration bugzilla@soe.ucsc.edu
• [Bug 226] if matching and non-existant resources bugzilla@soe.ucsc.edu
• [Bug 226] New: if matching and non-existant resources bugzilla@soe.ucsc.edu

Sunday, 29 January 2006

• [Bug 217] GULP integration bugzilla@soe.ucsc.edu
• [Bug 217] GULP integration bugzilla@soe.ucsc.edu
• [Bug 181] error element bugzilla@soe.ucsc.edu
• [Bug 13] new ETag requirements bugzilla@soe.ucsc.edu
• [Bug 13] new ETag requirements bugzilla@soe.ucsc.edu
• [Bug 161] EVALUATE_ALL_OF_IF_HEADER bugzilla@soe.ucsc.edu
• [Bug 161] EVALUATE_ALL_OF_IF_HEADER bugzilla@soe.ucsc.edu
• [Bug 161] EVALUATE_ALL_OF_IF_HEADER bugzilla@soe.ucsc.edu
• [Bug 219] mixed content in DAV:error bugzilla@soe.ucsc.edu
• [Bug 101] Extensibility for dav:owner bugzilla@soe.ucsc.edu
• [Bug 202] Move description of lock-null resources into appendix bugzilla@soe.ucsc.edu
• [Bug 202] Move description of lock-null resources into appendix bugzilla@soe.ucsc.edu
• [Bug 166] XML_GUIDELINES_CONFORMANCE bugzilla@soe.ucsc.edu
• [Bug 72] Review references section bugzilla@soe.ucsc.edu

Saturday, 28 January 2006

• Re: Relative references and whether requires an authority Julian Reschke
• Re: Relative references and whether requires an authority Lisa Dusseault
• Re: Relative references and whether requires an authority Julian Reschke
• [Bug 179] DAV:no-lock bugzilla@soe.ucsc.edu
• Re: Relative references and whether requires an authority Lisa Dusseault
• [Bug 211] Inconsistencies about Destination header bugzilla@soe.ucsc.edu
• [Bug 211] Inconsistencies about Destination header bugzilla@soe.ucsc.edu
• [Bug 35] RFC2606 compliance bugzilla@soe.ucsc.edu
• [Bug 35] RFC2606 compliance bugzilla@soe.ucsc.edu
• [Bug 152] SHOULD_A_SERVER_DETERMINE_MIMETYPE_OF_CONTENT bugzilla@soe.ucsc.edu
• [Bug 53] DAV:responsedescription content model bugzilla@soe.ucsc.edu
• [Bug 152] SHOULD_A_SERVER_DETERMINE_MIMETYPE_OF_CONTENT bugzilla@soe.ucsc.edu
• [Bug 188] PROPFIND include-dead-props bugzilla@soe.ucsc.edu
• [Bug 184] Clarifications requested for section 19.8 on hosting malicious content bugzilla@soe.ucsc.edu
• [Bug 53] DAV:responsedescription content model bugzilla@soe.ucsc.edu
• [Bug 46] URLs in Multistatus bugzilla@soe.ucsc.edu
• [Bug 210] incorrect statement on PROPPATCH and property recurrence bugzilla@soe.ucsc.edu
• Re: Relative references and whether requires an authority Julian Reschke

Friday, 27 January 2006

• [Bug 225] DAV:owner XML element definition lost bugzilla@soe.ucsc.edu
• [Bug 211] Inconsistencies about Destination header bugzilla@soe.ucsc.edu
• [Bug 210] incorrect statement on PROPPATCH and property recurrence bugzilla@soe.ucsc.edu
• [Bug 200] remove "bis" compliance class bugzilla@soe.ucsc.edu
• [Bug 188] PROPFIND include-dead-props bugzilla@soe.ucsc.edu
• [Bug 184] Clarifications requested for section 19.8 on hosting malicious content bugzilla@soe.ucsc.edu
• [Bug 179] DAV:no-lock bugzilla@soe.ucsc.edu
• [Bug 152] SHOULD_A_SERVER_DETERMINE_MIMETYPE_OF_CONTENT bugzilla@soe.ucsc.edu
• [Bug 97] new error code descriptions bugzilla@soe.ucsc.edu
• Relative references and whether requires an authority Lisa Dusseault
• [Bug 46] URLs in Multistatus bugzilla@soe.ucsc.edu
• [Bug 53] DAV:responsedescription content model bugzilla@soe.ucsc.edu
• [Bug 161] EVALUATE_ALL_OF_IF_HEADER bugzilla@soe.ucsc.edu
• [Bug 161] EVALUATE_ALL_OF_IF_HEADER bugzilla@soe.ucsc.edu
• [Bug 184] Clarifications requested for section 19.8 on hosting malicious content bugzilla@soe.ucsc.edu
• [Bug 46] URLs in Multistatus bugzilla@soe.ucsc.edu
• [Bug 166] XML_GUIDELINES_CONFORMANCE bugzilla@soe.ucsc.edu
• [Bug 219] mixed content in DAV:error bugzilla@soe.ucsc.edu
• [Bug 101] Extensibility for dav:owner bugzilla@soe.ucsc.edu
• [Bug 46] URLs in Multistatus bugzilla@soe.ucsc.edu
• Re: [Bug 184] Clarifications requested for section 19.8 on hosting malicious content Geoffrey M Clemm
• [Bug 184] Clarifications requested for section 19.8 on hosting malicious content bugzilla@soe.ucsc.edu
• Re: [Bug 184] Clarifications requested for section 19.8 on hosting malicious content Cullen Jennings
• [Bug 184] Clarifications requested for section 19.8 on hosting malicious content bugzilla@soe.ucsc.edu
• [Bug 184] Clarifications requested for section 19.8 on hosting malicious content bugzilla@soe.ucsc.edu
• Re: [Bug 184] Clarifications requested for section 19.8 on hosting malicious content Lisa Dusseault
• [Bug 67] non-ASCII characters bugzilla@soe.ucsc.edu
• [Bug 184] Clarifications requested for section 19.8 on hosting malicious content bugzilla@soe.ucsc.edu
• [Bug 53] DAV:responsedescription content model bugzilla@soe.ucsc.edu
• [Bug 67] non-ASCII characters bugzilla@soe.ucsc.edu
• [Bug 67] non-ASCII characters bugzilla@soe.ucsc.edu
• [Bug 200] remove "bis" compliance class bugzilla@soe.ucsc.edu
• [Bug 200] remove "bis" compliance class bugzilla@soe.ucsc.edu
• [Bug 200] remove "bis" compliance class bugzilla@soe.ucsc.edu
• [Bug 73] "Changes" section missing bugzilla@soe.ucsc.edu
• [Bug 72] Review references section bugzilla@soe.ucsc.edu
• [Bug 67] non-ASCII characters bugzilla@soe.ucsc.edu
• [Bug 35] RFC2606 compliance bugzilla@soe.ucsc.edu
• [Bug 221] condition code for write access to protected properties bugzilla@soe.ucsc.edu
• [Bug 221] condition code for write access to protected properties bugzilla@soe.ucsc.edu
• [Bug 211] Inconsistencies about Destination header bugzilla@soe.ucsc.edu
• [Bug 211] Inconsistencies about Destination header bugzilla@soe.ucsc.edu
• [Bug 184] Clarifications requested for section 19.8 on hosting malicious content bugzilla@soe.ucsc.edu
• [Bug 161] EVALUATE_ALL_OF_IF_HEADER bugzilla@soe.ucsc.edu
• [Bug 46] URLs in Multistatus bugzilla@soe.ucsc.edu
• [Bug 46] URLs in Multistatus bugzilla@soe.ucsc.edu

Thursday, 26 January 2006

• [Bug 217] GULP integration bugzilla@soe.ucsc.edu
• [Bug 217] GULP integration bugzilla@soe.ucsc.edu

Wednesday, 25 January 2006

• [Bug 184] Clarifications requested for section 19.8 on hosting malicious content bugzilla@soe.ucsc.edu
• [Bug 53] DAV:responsedescription content model bugzilla@soe.ucsc.edu
• [Bug 53] DAV:responsedescription content model bugzilla@soe.ucsc.edu
• [Bug 225] DAV:owner XML element definition lost bugzilla@soe.ucsc.edu
• [Bug 225] DAV:owner XML element definition lost bugzilla@soe.ucsc.edu
• [Bug 13] new ETag requirements bugzilla@soe.ucsc.edu

Tuesday, 24 January 2006

• [Bug 211] Inconsistencies about Destination header bugzilla@soe.ucsc.edu
• Re: Destination header syntax (Bug 211) and how WebDAV works with reverse proxies Julian Reschke
• Re: Destination header syntax (Bug 211) and how WebDAV works with reverse proxies Jim Whitehead
• [Bug 161] EVALUATE_ALL_OF_IF_HEADER bugzilla@soe.ucsc.edu
• Re: Destination header syntax (Bug 211) and how WebDAV works with reverse proxies Wilfredo Sánchez Vega

Monday, 23 January 2006

• I-D ACTION:draft-ietf-webdav-rfc2518bis-11.txt Internet-Drafts@ietf.org
• [Bug 223] Section organization for pre/postconditions bugzilla@soe.ucsc.edu
• [Bug 225] New: DAV:owner XML element definition lost bugzilla@soe.ucsc.edu
• Re: Bindings and permissions Julian Reschke
• Re: URL rewriting in PROPFIND responses (related to Bugzilla issue 46) Julian Reschke
• Re: Bindings and permissions Lisa Dusseault
• Re: URL rewriting in PROPFIND responses (related to Bugzilla issue 46) Lisa Dusseault

Sunday, 22 January 2006

• [Bug 86] DAV header definitions should use RFC3864 templates bugzilla@soe.ucsc.edu
• [Bug 85] clarification of live property behaviour vs namespace ops needed bugzilla@soe.ucsc.edu
• [Bug 80] Specify idempotence and safeness for all new methods bugzilla@soe.ucsc.edu
• [Bug 55] Multistatus format (empty) bugzilla@soe.ucsc.edu
• [Bug 53] DAV:responsedescription content model bugzilla@soe.ucsc.edu
• [Bug 110] COMPLIANCE_RESOURCE bugzilla@soe.ucsc.edu
• [Bug 44] OPTIONS * bugzilla@soe.ucsc.edu
• [Bug 42] Consider deprecating text/xml for XML request/response bodies bugzilla@soe.ucsc.edu
• [Bug 146] PROP_ROUNDTRIP bugzilla@soe.ucsc.edu
• [Bug 174] Terminology in 4.4: "namespace name in scope" bugzilla@soe.ucsc.edu
• [Bug 22] attributes on properties bugzilla@soe.ucsc.edu
• [Bug 10] Round-tripping various information in properties bugzilla@soe.ucsc.edu
• [Bug 46] URLs in Multistatus bugzilla@soe.ucsc.edu
• URL rewriting in PROPFIND responses (related to Bugzilla issue 46) Julian Reschke
• [Bug 46] URLs in Multistatus bugzilla@soe.ucsc.edu
• [Bug 224] add example for URI escaping in DAV:href bugzilla@soe.ucsc.edu
• [Bug 224] New: add example for URI escaping in DAV:href bugzilla@soe.ucsc.edu
• Re: Destination header syntax (Bug 211) and how WebDAV works with reverse proxies Julian Reschke
• [Bug 223] Section organization for pre/postconditions bugzilla@soe.ucsc.edu
• [Bug 181] error element bugzilla@soe.ucsc.edu
• [Bug 223] New: Section organization for pre/postconditions bugzilla@soe.ucsc.edu
• Re: Bindings and permissions Geoffrey M Clemm
• [Bug 222] Remove DTD fragments from pre/postcondition definitions when EMPTY bugzilla@soe.ucsc.edu
• [Bug 181] error element bugzilla@soe.ucsc.edu
• [Bug 222] New: Remove DTD fragments from pre/postcondition definitions when EMPTY bugzilla@soe.ucsc.edu
• [Bug 181] error element bugzilla@soe.ucsc.edu
• [Bug 221] condition code for write access to protected properties bugzilla@soe.ucsc.edu
• [Bug 221] New: condition code for write access to protected properties bugzilla@soe.ucsc.edu
• [Bug 220] Do status codes belong into pre/postcondition definitions? bugzilla@soe.ucsc.edu
• [Bug 220] Do status codes belong into pre/postcondition definitions? bugzilla@soe.ucsc.edu
• [Bug 181] error element bugzilla@soe.ucsc.edu
• [Bug 220] New: do belong status codes to pre/postcondition definitions? bugzilla@soe.ucsc.edu
• Re: Bindings and permissions Julian Reschke
• Re: Destination header syntax (Bug 211) and how WebDAV works with reverse proxies Jason Crawford
• Re: Bindings and permissions Lisa Dusseault
• Re: Destination header syntax (Bug 211) and how WebDAV works with reverse proxies Lisa Dusseault

Saturday, 21 January 2006

• Re: Bindings and permissions Geoffrey M Clemm
• Re: Bindings and permissions Cullen Jennings
• [Bug 211] Inconsistencies about Destination header bugzilla@soe.ucsc.edu
• Destination header syntax (Bug 211) and how WebDAV works with reverse proxies Julian Reschke
• [Bug 53] DAV:responsedescription content model bugzilla@soe.ucsc.edu
• [Bug 55] Multistatus format (empty) bugzilla@soe.ucsc.edu
• [Bug 86] DAV header definitions should use RFC3864 templates bugzilla@soe.ucsc.edu
• [Bug 86] DAV header definitions should use RFC3864 templates bugzilla@soe.ucsc.edu
• [Bug 213] Spec inconsistent on PROPFIND/Depth:infinity bugzilla@soe.ucsc.edu

Friday, 20 January 2006

• manage many servers Ha Pham
• [Bug 211] Inconsistencies about Destination header bugzilla@soe.ucsc.edu
• [Bug 181] error element bugzilla@soe.ucsc.edu
• [Bug 53] DAV:responsedescription content model bugzilla@soe.ucsc.edu
• [Bug 46] URLs in Multistatus bugzilla@soe.ucsc.edu
• [Bug 184] Clarifications requested for section 19.8 on hosting malicious content bugzilla@soe.ucsc.edu
• [Bug 184] Clarifications requested for section 19.8 on hosting malicious content bugzilla@soe.ucsc.edu
• [Bug 211] Inconsistencies about Destination header bugzilla@soe.ucsc.edu
• [Bug 210] incorrect statement on PROPPATCH and property recurrence bugzilla@soe.ucsc.edu
• [Bug 210] incorrect statement on PROPPATCH and property recurrence bugzilla@soe.ucsc.edu
• [Bug 213] Spec inconsistent on PROPFIND/Depth:infinity bugzilla@soe.ucsc.edu
• [Bug 213] Spec inconsistent on PROPFIND/Depth:infinity bugzilla@soe.ucsc.edu
• [Bug 188] PROPFIND include-dead-props bugzilla@soe.ucsc.edu
• [Bug 188] PROPFIND include-dead-props bugzilla@soe.ucsc.edu
• [Bug 181] error element bugzilla@soe.ucsc.edu
• [Bug 53] DAV:responsedescription content model bugzilla@soe.ucsc.edu
• [Bug 46] URLs in Multistatus bugzilla@soe.ucsc.edu
• [Bug 161] EVALUATE_ALL_OF_IF_HEADER bugzilla@soe.ucsc.edu
• [Bug 177] "PROPFIND status codes" section bugzilla@soe.ucsc.edu

Thursday, 19 January 2006

• [Bug 188] PROPFIND include-dead-props bugzilla@soe.ucsc.edu

Wednesday, 18 January 2006

• [Bug 188] PROPFIND include-dead-props bugzilla@soe.ucsc.edu
• [Bug 188] PROPFIND include-dead-props bugzilla@soe.ucsc.edu
• Status of 2518bis Cullen Jennings
• [Bug 219] mixed content in DAV:error bugzilla@soe.ucsc.edu
• [Bug 219] mixed content in DAV:error bugzilla@soe.ucsc.edu
• [Bug 161] EVALUATE_ALL_OF_IF_HEADER bugzilla@soe.ucsc.edu
• [Bug 161] EVALUATE_ALL_OF_IF_HEADER bugzilla@soe.ucsc.edu
• [Bug 188] PROPFIND include-dead-props bugzilla@soe.ucsc.edu
• [Bug 188] PROPFIND include-dead-props bugzilla@soe.ucsc.edu
• [Bug 218] broken date format in example 8.2.6 bugzilla@soe.ucsc.edu
• [Bug 177] "PROPFIND status codes" section bugzilla@soe.ucsc.edu
• [Bug 177] "PROPFIND status codes" section bugzilla@soe.ucsc.edu
• [Bug 10] Round-tripping various information in properties bugzilla@soe.ucsc.edu
• [Bug 152] SHOULD_A_SERVER_DETERMINE_MIMETYPE_OF_CONTENT bugzilla@soe.ucsc.edu
• [Bug 152] SHOULD_A_SERVER_DETERMINE_MIMETYPE_OF_CONTENT bugzilla@soe.ucsc.edu
• [Bug 80] Specify idempotence and safeness for all new methods bugzilla@soe.ucsc.edu
• [Bug 80] Specify idempotence and safeness for all new methods bugzilla@soe.ucsc.edu
• [Bug 97] new error code descriptions bugzilla@soe.ucsc.edu
• [Bug 97] new error code descriptions bugzilla@soe.ucsc.edu
• [Bug 42] Consider deprecating text/xml for XML request/response bodies bugzilla@soe.ucsc.edu
• [Bug 44] OPTIONS * bugzilla@soe.ucsc.edu
• [Bug 44] OPTIONS * bugzilla@soe.ucsc.edu
• [Bug 42] Consider deprecating text/xml for XML request/response bodies bugzilla@soe.ucsc.edu
• [Bug 10] Round-tripping various information in properties bugzilla@soe.ucsc.edu
• [Bug 217] GULP integration bugzilla@soe.ucsc.edu
• [Bug 217] GULP integration bugzilla@soe.ucsc.edu
• Re: GULP as pure model, draft 2 Julian Reschke

Tuesday, 17 January 2006

• [Bug 166] XML_GUIDELINES_CONFORMANCE bugzilla@soe.ucsc.edu
• [Bug 101] Extensibility for dav:owner bugzilla@soe.ucsc.edu
• [Bug 219] New: mixed content in DAV:error bugzilla@soe.ucsc.edu
• [Bug 174] Terminology in 4.4: "namespace name in scope" bugzilla@soe.ucsc.edu
• [Bug 146] PROP_ROUNDTRIP bugzilla@soe.ucsc.edu
• [Bug 22] attributes on properties bugzilla@soe.ucsc.edu
• [Bug 10] Round-tripping various information in properties bugzilla@soe.ucsc.edu
• [Bug 42] Consider deprecating text/xml for XML request/response bodies bugzilla@soe.ucsc.edu
• [Bug 110] COMPLIANCE_RESOURCE bugzilla@soe.ucsc.edu
• [Bug 44] OPTIONS * bugzilla@soe.ucsc.edu
• [Bug 46] URLs in Multistatus bugzilla@soe.ucsc.edu
• [Bug 46] URLs in Multistatus bugzilla@soe.ucsc.edu
• [Bug 53] DAV:responsedescription content model bugzilla@soe.ucsc.edu
• Re: 'responsedescription' element Julian Reschke
• [Bug 80] Specify idempotence and safeness for all new methods bugzilla@soe.ucsc.edu
• [Bug 97] new error code descriptions bugzilla@soe.ucsc.edu
• [Bug 108] PROP_ATTR bugzilla@soe.ucsc.edu
• [Bug 10] Round-tripping various information in properties bugzilla@soe.ucsc.edu
• [Bug 108] PROP_ATTR bugzilla@soe.ucsc.edu
• [Bug 147] CLARIFY_UNTAGGED_IF_HEADER_APPLICATION bugzilla@soe.ucsc.edu
• [Bug 152] SHOULD_A_SERVER_DETERMINE_MIMETYPE_OF_CONTENT bugzilla@soe.ucsc.edu
• [Bug 177] "PROPFIND status codes" section bugzilla@soe.ucsc.edu
• [Bug 179] DAV:no-lock bugzilla@soe.ucsc.edu
• [Bug 188] PROPFIND include-dead-props bugzilla@soe.ucsc.edu
• Re: GULP as pure model, draft 2 Geoffrey M Clemm
• [Bug 218] broken date format in example 8.2.6 bugzilla@soe.ucsc.edu
• [Bug 218] broken date format in example 8.2.6 bugzilla@soe.ucsc.edu
• [Bug 216] bad sectiion reference in 9.1 bugzilla@soe.ucsc.edu
• [Bug 188] PROPFIND include-dead-props bugzilla@soe.ucsc.edu
• [Bug 179] DAV:no-lock bugzilla@soe.ucsc.edu
• [Bug 177] "PROPFIND status codes" section bugzilla@soe.ucsc.edu
• [Bug 166] XML_GUIDELINES_CONFORMANCE bugzilla@soe.ucsc.edu
• [Bug 152] SHOULD_A_SERVER_DETERMINE_MIMETYPE_OF_CONTENT bugzilla@soe.ucsc.edu
• [Bug 147] CLARIFY_UNTAGGED_IF_HEADER_APPLICATION bugzilla@soe.ucsc.edu
• [Bug 143] LOCK_RENEWAL_SHOULD_NOT_USE_IF_HEADER bugzilla@soe.ucsc.edu
• [Bug 132] DEPTH_LOCK_AND_IF bugzilla@soe.ucsc.edu

Monday, 16 January 2006

• [Bug 124] REPORT_OTHER_RESOURCE_LOCKED bugzilla@soe.ucsc.edu
• [Bug 108] PROP_ATTR bugzilla@soe.ucsc.edu
• [Bug 99] Risks Connected with Lock Tokens bugzilla@soe.ucsc.edu
• [Bug 97] new error code descriptions bugzilla@soe.ucsc.edu
• [Bug 86] DAV header definitions should use RFC3864 templates bugzilla@soe.ucsc.edu
• [Bug 80] Specify idempotence and safeness for all new methods bugzilla@soe.ucsc.edu
• [Bug 55] Multistatus format (empty) bugzilla@soe.ucsc.edu
• 'responsedescription' element Lisa Dusseault
• [Bug 53] DAV:responsedescription content model bugzilla@soe.ucsc.edu
• [Bug 166] XML_GUIDELINES_CONFORMANCE bugzilla@soe.ucsc.edu
• [Bug 101] Extensibility for dav:owner bugzilla@soe.ucsc.edu
• [Bug 46] URLs in Multistatus bugzilla@soe.ucsc.edu
• [Bug 110] COMPLIANCE_RESOURCE bugzilla@soe.ucsc.edu
• [Bug 44] OPTIONS * bugzilla@soe.ucsc.edu
• [Bug 42] Consider deprecating text/xml for XML request/response bodies bugzilla@soe.ucsc.edu
• [Bug 146] PROP_ROUNDTRIP bugzilla@soe.ucsc.edu
• [Bug 10] Round-tripping various information in properties bugzilla@soe.ucsc.edu
• [Bug 22] attributes on properties bugzilla@soe.ucsc.edu
• [Bug 174] Terminology in 4.4: "namespace name in scope" bugzilla@soe.ucsc.edu
• GULP as pure model, draft 2 Lisa Dusseault
• Re: GULP as pure model Julian Reschke
• Re: GULP as pure model Lisa Dusseault
• Re: GULP as pure model Julian Reschke

Sunday, 15 January 2006

• [Bug 35] RFC2606 compliance bugzilla@soe.ucsc.edu
• [Bug 218] New: broken date format in example 8.2.6 bugzilla@soe.ucsc.edu
• Re: Interaction of WebDAV with HTTPS and problems opening files Julian Reschke
• [Bug 13] new ETag requirements bugzilla@soe.ucsc.edu

Saturday, 14 January 2006

• [Bug 181] error element bugzilla@soe.ucsc.edu
• [Bug 152] SHOULD_A_SERVER_DETERMINE_MIMETYPE_OF_CONTENT bugzilla@soe.ucsc.edu
• [Bug 132] DEPTH_LOCK_AND_IF bugzilla@soe.ucsc.edu
• [Bug 80] Specify idempotence and safeness for all new methods bugzilla@soe.ucsc.edu
• [Bug 80] Specify idempotence and safeness for all new methods bugzilla@soe.ucsc.edu
• [Bug 80] Specify idempotence and safeness for all new methods bugzilla@soe.ucsc.edu

Friday, 13 January 2006

• Re: Process on open RFC2518bis issues Geoffrey M Clemm
• Re: Process on open RFC2518bis issues Julian Reschke
• [Bug 166] XML_GUIDELINES_CONFORMANCE bugzilla@soe.ucsc.edu
• Re: Process on open RFC2518bis issues Cullen Jennings
• [Bug 80] Specify idempotence and safeness for all new methods bugzilla@soe.ucsc.edu
• [Bug 80] Specify idempotence and safeness for all new methods bugzilla@soe.ucsc.edu
• [Bug 101] Extensibility for dav:owner bugzilla@soe.ucsc.edu
• [Bug 10] Round-tripping various information in properties bugzilla@soe.ucsc.edu
• [Bug 10] Round-tripping various information in properties bugzilla@soe.ucsc.edu
• [Bug 44] OPTIONS * bugzilla@soe.ucsc.edu
• [Bug 44] OPTIONS * bugzilla@soe.ucsc.edu
• [Bug 147] CLARIFY_UNTAGGED_IF_HEADER_APPLICATION bugzilla@soe.ucsc.edu

Thursday, 12 January 2006

• Re: Interaction of WebDAV with HTTPS and problems opening files Joachim Feise
• Re: Interaction of WebDAV with HTTPS and problems opening files Julian Reschke
• Re: Interaction of WebDAV with HTTPS and problems opening files Ian Stokes-Rees
• [Bug 177] "PROPFIND status codes" section bugzilla@soe.ucsc.edu
• Re: Interaction of WebDAV with HTTPS and problems opening files Julian Reschke
• Interaction of WebDAV with HTTPS and problems opening files Ian Stokes-Rees

Wednesday, 11 January 2006

• [Bug 53] DAV:responsedescription content model bugzilla@soe.ucsc.edu
• [Bug 53] DAV:responsedescription content model bugzilla@soe.ucsc.edu
• [Bug 42] Consider deprecating text/xml for XML request/response bodies bugzilla@soe.ucsc.edu
• [Bug 142] URL_ENCODING_ISSUES bugzilla@soe.ucsc.edu
• [Bug 142] URL_ENCODING_ISSUES bugzilla@soe.ucsc.edu
• [Bug 142] URL_ENCODING_ISSUES bugzilla@soe.ucsc.edu
• [Bug 158] SHOULD_WE_SUPPORT_IRIS_AND_CHARMOD bugzilla@soe.ucsc.edu
• [Bug 147] CLARIFY_UNTAGGED_IF_HEADER_APPLICATION bugzilla@soe.ucsc.edu
• [Bug 132] DEPTH_LOCK_AND_IF bugzilla@soe.ucsc.edu
• [Bug 142] URL_ENCODING_ISSUES bugzilla@soe.ucsc.edu
• [Bug 44] OPTIONS * bugzilla@soe.ucsc.edu
• [Bug 177] "PROPFIND status codes" section bugzilla@soe.ucsc.edu
• [Bug 158] SHOULD_WE_SUPPORT_IRIS_AND_CHARMOD bugzilla@soe.ucsc.edu
• [Bug 100] "Notes on HTTP Client Compatibility" useful? bugzilla@soe.ucsc.edu
• [Bug 158] SHOULD_WE_SUPPORT_IRIS_AND_CHARMOD bugzilla@soe.ucsc.edu
• [Bug 142] URL_ENCODING_ISSUES bugzilla@soe.ucsc.edu
• [Bug 152] SHOULD_A_SERVER_DETERMINE_MIMETYPE_OF_CONTENT bugzilla@soe.ucsc.edu
• [Bug 158] SHOULD_WE_SUPPORT_IRIS_AND_CHARMOD bugzilla@soe.ucsc.edu
• [Bug 13] new ETag requirements bugzilla@soe.ucsc.edu
• [Bug 13] new ETag requirements bugzilla@soe.ucsc.edu
• [Bug 179] DAV:no-lock bugzilla@soe.ucsc.edu
• [Bug 179] DAV:no-lock bugzilla@soe.ucsc.edu
• [Bug 197] LOCK_ISSUES_IF_HEADER bugzilla@soe.ucsc.edu
• [Bug 143] LOCK_RENEWAL_SHOULD_NOT_USE_IF_HEADER bugzilla@soe.ucsc.edu
• [Bug 196] LOCK_ISSUES_ERROR_CODES bugzilla@soe.ucsc.edu
• Re: Process on open RFC2518bis issues Geoffrey M Clemm
• Re: Process on open RFC2518bis issues Cullen Jennings
• [Bug 211] Inconsistencies about Destination header bugzilla@soe.ucsc.edu
• Re: Process on open RFC2518bis issues Geoffrey M Clemm
• Re: Process on open RFC2518bis issues Cullen Jennings
• Re: Re-using 414 status codes (related to Bug 31) Cullen Jennings
• Re: Re-using 414 status codes (related to Bug 31) Julian Reschke
• Re: Process on open RFC2518bis issues Julian Reschke
• Re: Re-using 414 status codes (related to Bug 31) Cullen Jennings
• Re: Re-using 414 status codes (related to Bug 31) Julian Reschke
• Re: Re-using 414 status codes (related to Bug 31) Cullen Jennings
• Re: Process on open RFC2518bis issues Cullen Jennings

Tuesday, 10 January 2006

• [Bug 10] Round-tripping various information in properties bugzilla@soe.ucsc.edu
• [Bug 146] PROP_ROUNDTRIP bugzilla@soe.ucsc.edu
• [Bug 22] attributes on properties bugzilla@soe.ucsc.edu
• [Bug 174] Terminology in 4.4: "namespace name in scope" bugzilla@soe.ucsc.edu
• [Bug 10] Round-tripping various information in properties bugzilla@soe.ucsc.edu
• Re: Process on open RFC2518bis issues Tyler Batory
• Re: Process on open RFC2518bis issues Geoffrey M Clemm
• GULP as pure model Lisa Dusseault

Monday, 9 January 2006

• LNRs (lock null resources) in RFC2518bis Julian Reschke
• Re: Process on open RFC2518bis issues Julian Reschke
• Re: Process on open RFC2518bis issues Cullen Jennings

Sunday, 8 January 2006

• Re: Issue 147 - Depth vs Conditional headers Julian Reschke
• [Bug 211] Inconsistencies about Destination header bugzilla@soe.ucsc.edu
• [Bug 217] New: GULP integration bugzilla@soe.ucsc.edu
• [Bug 211] Inconsistencies about Destination header bugzilla@soe.ucsc.edu
• [Bug 211] Inconsistencies about Destination header bugzilla@soe.ucsc.edu
• [Bug 44] OPTIONS * bugzilla@soe.ucsc.edu

Saturday, 7 January 2006

• [Bug 177] "PROPFIND status codes" section bugzilla@soe.ucsc.edu
• [Bug 106] COPY and the Overwrite Header vs merge behaviour desc added bugzilla@soe.ucsc.edu
• [Bug 18] no record of consensus for force-authenticate bugzilla@soe.ucsc.edu
• [Bug 143] LOCK_RENEWAL_SHOULD_NOT_USE_IF_HEADER bugzilla@soe.ucsc.edu
• [Bug 188] PROPFIND include-dead-props bugzilla@soe.ucsc.edu
• [Bug 152] SHOULD_A_SERVER_DETERMINE_MIMETYPE_OF_CONTENT bugzilla@soe.ucsc.edu
• [Bug 55] Multistatus format (empty) bugzilla@soe.ucsc.edu
• Re: Issue 147 - Depth vs Conditional headers Geoffrey M Clemm
• [Bug 100] "Notes on HTTP Client Compatibility" useful? bugzilla@soe.ucsc.edu
• [Bug 98] new error code descriptions, continued bugzilla@soe.ucsc.edu
• [Bug 97] new error code descriptions bugzilla@soe.ucsc.edu
• [Bug 109] CONSISTENCY bugzilla@soe.ucsc.edu
• [Bug 10] Round-tripping various information in properties bugzilla@soe.ucsc.edu
• [Bug 108] PROP_ATTR bugzilla@soe.ucsc.edu
• [Bug 86] DAV header definitions should use RFC3864 templates bugzilla@soe.ucsc.edu
• [Bug 86] DAV header definitions should use RFC3864 templates bugzilla@soe.ucsc.edu
• [Bug 86] DAV header definitions should use RFC3864 templates bugzilla@soe.ucsc.edu
• [Bug 166] XML_GUIDELINES_CONFORMANCE bugzilla@soe.ucsc.edu
• Re: Issue 147 - Depth vs Conditional headers Julian Reschke
• Re: Issue 147 - Depth vs Conditional headers Geoffrey M Clemm
• [Bug 42] Consider deprecating text/xml for XML request/response bodies bugzilla@soe.ucsc.edu
• [Bug 166] XML_GUIDELINES_CONFORMANCE bugzilla@soe.ucsc.edu
• [Bug 46] URLs in Multistatus bugzilla@soe.ucsc.edu
• [Bug 216] New: bad sectiion reference in 9.1 bugzilla@soe.ucsc.edu
• [Bug 99] Risks Connected with Lock Tokens bugzilla@soe.ucsc.edu
• [Bug 147] CLARIFY_UNTAGGED_IF_HEADER_APPLICATION bugzilla@soe.ucsc.edu
• [Bug 147] CLARIFY_UNTAGGED_IF_HEADER_APPLICATION bugzilla@soe.ucsc.edu
• Issue 147 - Depth vs Conditional headers Julian Reschke

Friday, 6 January 2006

• Re: Question on GULP - resources added to locked collection Geoffrey M Clemm
• [Bug 213] Spec inconsistent on PROPFIND/Depth:infinity bugzilla@soe.ucsc.edu
• [Bug 213] Spec inconsistent on PROPFIND/Depth:infinity bugzilla@soe.ucsc.edu
• [Bug 211] Inconsistencies about Destination header bugzilla@soe.ucsc.edu
• [Bug 213] Spec inconsistent on PROPFIND/Depth:infinity bugzilla@soe.ucsc.edu
• [Bug 213] Spec inconsistent on PROPFIND/Depth:infinity bugzilla@soe.ucsc.edu
• [Bug 163] REMOVE_NOT_SUPPORT_FROM_IF_HEADERS bugzilla@soe.ucsc.edu
• [Bug 197] LOCK_ISSUES_IF_HEADER bugzilla@soe.ucsc.edu
• [Bug 196] LOCK_ISSUES_ERROR_CODES bugzilla@soe.ucsc.edu
• [Bug 130] IF_AND_AUTH bugzilla@soe.ucsc.edu
• [Bug 202] Move description of lock-null resources into appendix bugzilla@soe.ucsc.edu
• [Bug 101] Extensibility for dav:owner bugzilla@soe.ucsc.edu
• [Bug 101] Extensibility for dav:owner bugzilla@soe.ucsc.edu
• [Bug 92] lock owner description bugzilla@soe.ucsc.edu
• [Bug 138] UNLOCK_WHAT_URL bugzilla@soe.ucsc.edu
• [Bug 133] LOCK_SEMANTICS bugzilla@soe.ucsc.edu
• [Bug 92] lock owner description bugzilla@soe.ucsc.edu
• [Bug 92] lock owner description bugzilla@soe.ucsc.edu
• [Bug 215] Broken section organization bugzilla@soe.ucsc.edu
• [Bug 214] Consistent section titles for method descriptions bugzilla@soe.ucsc.edu
• Re: Question on GULP - resources added to locked collection Lisa Dusseault
• [Bug 95] possible LOCK response codes bugzilla@soe.ucsc.edu
• [Bug 50] Property teminology inconsistent with RFC3253 bugzilla@soe.ucsc.edu
• [Bug 121] OVERWRITE_DELETE_ERROR_STATUS bugzilla@soe.ucsc.edu
• Fwd: [Moderator Action] Re: [Ietf-http-auth] Clients desiring to authenticate Jim Whitehead
• [Bug 53] DAV:responsedescription content model bugzilla@soe.ucsc.edu
• [Bug 214] Consistent section titles for method descriptions bugzilla@soe.ucsc.edu
• [Bug 215] New: Broken section organization bugzilla@soe.ucsc.edu
• [Bug 214] New: Consistents section titles for method descriptions bugzilla@soe.ucsc.edu
• [Bug 80] Specify idempotence and safeness for all new methods bugzilla@soe.ucsc.edu
• Re: Process on open RFC2518bis issues Geoffrey M Clemm
• Process on open RFC2518bis issues Julian Reschke

Thursday, 5 January 2006

• Re: [Ietf-http-auth] Clients desiring to authenticate Lisa Dusseault
• Fwd: [Moderator Action] Re: [Ietf-http-auth] Clients desiring to authenticate Jim Whitehead
• Clients desiring to authenticate Lisa Dusseault

Wednesday, 4 January 2006

• Re: Cacheability; MKCOL idempotent? Julian Reschke
• Re: Cacheability; MKCOL idempotent? Julian Reschke
• Fwd: [Moderator Action] Appendix D comments Jim Whitehead
• Re: Status of Bugzilla Bug 10, Round-tripping various information in properties Wilfredo Sánchez Vega
• Re: Status of Bugzilla Bug 10, Round-tripping various information in properties Wilfredo Sánchez Vega
• (semi)permanent agenda for upcoming telecons Elias Sinderson
• [Bug 200] remove "bis" compliance class bugzilla@soe.ucsc.edu
• Re: Behavior of getlastmodified, particularly with MOVE Geoffrey M Clemm
• [Bug 147] CLARIFY_UNTAGGED_IF_HEADER_APPLICATION bugzilla@soe.ucsc.edu
• [Bug 147] CLARIFY_UNTAGGED_IF_HEADER_APPLICATION bugzilla@soe.ucsc.edu
• [Bug 124] REPORT_OTHER_RESOURCE_LOCKED bugzilla@soe.ucsc.edu
• [Bug 124] REPORT_OTHER_RESOURCE_LOCKED bugzilla@soe.ucsc.edu
• [Bug 121] OVERWRITE_DELETE_ERROR_STATUS bugzilla@soe.ucsc.edu
• [Bug 121] OVERWRITE_DELETE_ERROR_STATUS bugzilla@soe.ucsc.edu
• Behavior of getlastmodified, particularly with MOVE Lisa Dusseault
• [Bug 95] possible LOCK response codes bugzilla@soe.ucsc.edu
• [Bug 85] clarification of live property behaviour vs namespace ops needed bugzilla@soe.ucsc.edu
• [Bug 85] clarification of live property behaviour vs namespace ops needed bugzilla@soe.ucsc.edu
• [Bug 10] Round-tripping various information in properties bugzilla@soe.ucsc.edu
• [Bug 174] Terminology in 4.4: "namespace name in scope" bugzilla@soe.ucsc.edu
• [Bug 146] PROP_ROUNDTRIP bugzilla@soe.ucsc.edu
• [Bug 22] attributes on properties bugzilla@soe.ucsc.edu
• [Bug 10] Round-tripping various information in properties bugzilla@soe.ucsc.edu
• [Bug 80] Specify idempotence and safeness for all new methods bugzilla@soe.ucsc.edu
• [Bug 80] Specify idempotence and safeness for all new methods bugzilla@soe.ucsc.edu
• [Bug 10] Round-tripping various information in properties bugzilla@soe.ucsc.edu

Tuesday, 3 January 2006

• Re: Cacheability; MKCOL idempotent? Geoffrey M Clemm
• I-D ACTION:draft-ietf-webdav-rfc2518bis-10.txt Internet-Drafts@ietf.org
• Cacheability; MKCOL idempotent? Julian Reschke

Sunday, 1 January 2006

• [Bug 50] Property teminology inconsistent with RFC3253 bugzilla@soe.ucsc.edu

Last message date: Friday, 31 March 2006 15:06:04 UTC