WebDAV -- Advanced Status Reporting
draft-ietf-webdav-status-00
| Document | Type |
Expired Internet-Draft
(webdav WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Lisa M. Dusseault | ||
| Last updated | 2001-01-29 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
HTTP 1.1 [2] defines 20 status codes: 100-101, 200-206, 300-305, 400-415, and 500-505. The WebDAV RFC [3] adds six more: 102, 207, 422, 423, 424 and 507. However, WebDAV implementers have found this to be insufficient. The space of status codes available is limited, but even if it were not, additional information would often be very helpful. WebDAV clients frequently need to be able to present distinct options and helpful information to users, and sometimes cients might even be able to deal with errors automatically.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)