DAV::getlastmodified

###Purpose

Contains the Last-Modified header value (from Section 14.29 of RFC 2616) as it would be returned by a GET method without accept headers.

###Value

rfc1123-date (defined in Section 3.3.1 of RFC 2616)

###Protected

SHOULD be protected because some clients may rely on the value for appropriate caching behavior, or on the value of the Last-Modified header to which this property is linked.

###COPY/MOVE behavior

This property value is dependent on the last modified date of the destination resource, not the value of the property on the source resource. Note that some server implementations use the file system date modified value for the DAV:getlastmodified value, and this can be preserved in a MOVE even when the HTTP Last-Modified value SHOULD change. Note that since RFC 2616 requires clients to use ETags where provided, a server implementing ETags can count on clients using a much better mechanism than modification dates for offline synchronization or cache control. Also note the considerations in Section 8.8.

###Description

The last-modified date on a resource SHOULD only reflect changes in the body (the GET responses) of the resource. A change in a property only SHOULD NOT cause the last-modified date to change, because clients MAY rely on the last-modified date to know when to overwrite the existing body. The DAV:getlastmodified property MUST be defined on any DAV-compliant resource that returns the Last-Modified header in response to a GET.

DTD

<!ELEMENT getlastmodified (#PCDATA) >