Miguel Figueiredo wrote:
Hello mate,
If you need to do change the lastModified time of a resource, I would
consider that an hacker wish ;)
No way you're going to be able to that, especially if you are using the
client API. You would need to change server behavior, and in a way that the
server would not follow webdav specification directives. The reason is
pretty straightforward: webdav specification states that resources have
"live" and "dead" properties, being the dead properties the ones we can
PROPPATCH, that is, we can create, update and remove them from the resource.
The live properties values, like lastModified, creationDate, contentLength,
contentType, are calculated in real time (maybe stored afterwards) with
server information. For that reason, they are protected, and can't be
changed by the user (I'll just copy paste and excerpt from rfc4918):
"
Live Property - A property whose semantics and syntax are enforced by
the server. For example, the live property DAV:getcontentlength has
its value, the length of the entity returned by a GET request,
automatically calculated by the server.
"
...
Well.
This means that a server is *allowed* to reject a request setting
DAV:getlastmodified. But it doesn't have to.
Best regards, Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
