WebDAV Working Group Agenda IETF-49, San Diego Dec minutes: agenda bashing, find note-taker 50 minutes: Open issues & review of Access Control Eric Sedlar, Oracle Corporation Geoffrey Clemm, Rational Software 25 minutes: Improved status reporting Lisa Dusseault, Xythos 40 minutes: General-purpose WebDAV facilities in DeltaV Jim Amsden, IBM

Advanced Status Reporting for WebDAV Lisa Dusseault, Xythos

Use case examples Access Control Server does not support right ‘readACL’ Principal does not exist Versioning Cannot modify existing version Cannot rename working resource Regular WebDAV Better 412 detail Which precondition failed Better 400 detail What part of request is bad

Goals Extensible Error codes must not be restricted by finite set of codes Name specific entities the locked file blocking a MOVE of a collection A right in an ACL not supported by server The header that had syntax errors Report errors for multiple entities E.g. Several locked documents Backward-compatible

Overall design Response contains in XML body IF client asks for it Except for 200, 207, 1xx, 204 and 304 contains for overall (summary) information for individual resources specified by URI in tag Machine-interpretable error code and details Freeform text to present to user In language specified by Accept-language

Example detail-codes Stand-alone detail-codes Detail-code with sub-structure: write-prop

A simple example response HTTP/ Bad Request Content-type: text/xml; charset=“utf-8” Content-length: 123 Le corps “XML” de la démande était mal- formé

Example: 423 Locked response to MOVE One or more members of “/mydir" was locked. HTTP/ Locked

Open Issues Client advertisement of support Ability to describe status-code “levels” Fatal, warning, informational How to represent multiple errors with one resource Multiple elements each with single element Unique element by, but containing multiple elements or sub- elements