HTTP/1.1
Click on the red underlined text to get to the source
...
This document describes an extension to the HTTP/1.1 protocol that
allows clients to perform remote web content authoring operations.
...
... method parameter information was exclusively encoded in
HTTP headers. Unlike HTTP/1.1, WebDAV encodes method parameter
...
...
While the status codes provided by HTTP/1.1 are sufficient to
describe most error conditions encountered by WebDAV ...
...
Since this document describes a set of extensions to the HTTP/1.1
protocol, the augmented BNF used herein to describe protocol elements ...
... A resource which responds with a 404 (Not Found) to
any HTTP/1.1 or DAV method except for PUT, MKCOL, OPTIONS and LOCK.
...
... method to create new collection
resources, rather than using the existing HTTP/1.1 PUT or POST
method, for the following reasons:
...
...
In HTTP/1.1, the PUT method is defined to store the request body at
the location specified by the Request-URI ...
... MUST respond with a 404 (Not Found) or 405 (Method Not Allowed) to
any HTTP/1.1 or DAV methods except for PUT, MKCOL, OPTIONS, PROPFIND ...
... >>Response
HTTP/1.1 204 No Content
...
... </R:author>
</D:prop>
<D:status>HTTP/1.1 200 OK</D:status>
</D:propstat>
<D:propstat>
...
... <D:propstat>
<D:prop><R:DingALing/><R:Random/></D:prop>
<D:status>HTTP/1.1 403 Forbidden</D:status>
<D:responsedescription> The user does not have access to
the DingALing property.
...
... </D:supportedlock>
</D:prop>
<D:status>HTTP/1.1 200 OK</D:status>
</D:propstat>
</D:response>
...
... </D:supportedlock>
</D:prop>
<D:status>HTTP/1.1 200 OK</D:status>
</D:propstat>
</D:response>
...
... <supportedlock/>
</prop>
<status>HTTP/1.1 200 OK</status>
</propstat>
</response>
...
... <supportedlock/>
</prop>
<status>HTTP/1.1 200 OK</status>
</propstat>
</response>
...
... <D:propstat>
<D:prop><Z:Authors/></D:prop>
<D:status>HTTP/1.1 424 Failed Dependency</D:status>
</D:propstat>
<D:propstat>
...
... <D:propstat>
<D:prop><Z:Copyright-Owner/></D:prop>
<D:status>HTTP/1.1 409 Conflict</D:status>
</D:propstat>
<D:responsedescription> Copyright Owner can not be deleted ...
... <d:response>
<d:href>http://www.foo.bar/container/resource3</d:href>
<d:status>HTTP/1.1 423 Locked</d:status>
</d:response>
</d:multistatus>
...
... COPY for HTTP/1.1 resources ...
... >>Response
HTTP/1.1 204 No Content
...
... >>Response
HTTP/1.1 412 Precondition Failed
...
... <d:response>
<d:href>http://www.foo.bar/othercontainer/R2/</d:href>
<d:status>HTTP/1.1 412 Precondition Failed</d:status>
</d:response>
</d:multistatus>
...
... >>Response
HTTP/1.1 201 Created
Location: http://www.ics.uci.edu/users/f/fielding/index.html
...
... <d:response>
<d:href>http://www.foo.bar/othercontainer/C2/</d:href>
<d:status>HTTP/1.1 423 Locked</d:status>
</d:response>
</d:multistatus>
...
... webdav.sb.aol.com/webdav/secret</D:href>
<D:status>HTTP/1.1 403 Forbidden</D:status>
</D:response>
<D:response>
...
... <D:propstat>
<D:prop><D:lockdiscovery/></D:prop>
<D:status>HTTP/1.1 424 Failed Dependency</D:status>
</D:propstat>
</D:response>
...
... >>Response
HTTP/1.1 204 No Content
...
... HTTP requires non-understood
headers to be ignored. When communicating with HTTP/1.1 proxies, the
"Cache-Control ...
... header appears to duplicate
the functionality of the If-Match: * header of HTTP/1.1, If-Match
applies only to the Request-URI, and not to the Destination ...
... Status Code Extensions to HTTP/1.1 ...
... </D:lockdiscovery>
</D:prop>
<D:status>HTTP/1.1 200 OK</D:status>
</D:propstat>
</D:response>
...
... </D:supportedlock>
</D:prop>
<D:status>HTTP/1.1 200 OK</D:status>
</D:propstat>
</D:response>
...
...
Since this document describes extensions to the HTTP/1.1 protocol,
minimally all DAV compliant resources, clients ...
...
For error reporting, we follow the convention of HTTP/1.1 status
codes, including with each status code a short, English description
...
... resource as the password may be intercepted. Since Basic
authentication for HTTP/1.1 performs essentially clear text
transmission of a password, Basic authentication ...
...
HTTP/1.1 warns against providing read access to script code because
it may contain sensitive information. Yet WebDAV, via its source
...
... link facility, can potentially provide a URI for script resources so
they may be authored. For HTTP/1.1, a server could reasonably
prevent access to source resources due to the predominance of read-
only access. WebDAV ...