Open onnozweers opened 1 year ago
Ah, I found an error in the PROPPATCH request. Trying again with:
onno$ cat proppatch.xml
<?xml version="1.0"?>
<d:propertyupdate xmlns:d="DAV:">
<d:set>
<d:prop>
<d:getlastmodified>Sun, 12 Aug 1928 12:10:00 GMT</d:getlastmodified>
</d:prop>
</d:set>
</d:propertyupdate>
This time I got an error: <d:status>HTTP/1.1 403</d:status>
(Forbidden).
In the door log:
13 Oct 2022 17:34:38 (webdav2881-penguin12) [door:webdav2881-penguin12@webdav2881-penguin12Domain:AAXq7D9GkSA] property is not writable in source: class io.milton.http.webdav.WebDavProtocol
In the access log:
level=INFO ts=2022-10-13T17:34:38.330+0200 event=org.dcache.webdav.request request.method=PROPPATCH request.url=https://penguin12.grid.surfsara.nl:2881/pnfs/grid.sara.nl/data/users/onno/README.txt response.code=207 response.reason=Multi-status socket.remote=145.38.218.162:50128 user-agent=curl/7.29.0 user.mapped=31029:31040,44736,40304,44436,47798,41385,30013,30014 duration=5
Here the response code is 207, not 403.
Dear dCache developers,
We have a user who wants to upload a dataset while retaining the original modification dates. I don't expect that dCache does that by default. So I looked into the WebDAV PROPPATCH operation, to try and modify the modification date. Here's what I tried:
First a PROPFIND to find out the names of the properties:
I see a getlastmodified, that looks good.
From the user manual I saw some examples on how to do a PROPPATCH.
I created a request:
Sending the request:
The request does not appear in the billing file.
In the access file webdav2881-penguin12Domain.access:
webdav2881-penguin12Domain.access:level=INFO ts=2022-10-13T14:01:44.795+0200 event=org.dcache.webdav.request request.method=PROPPATCH request.url=https://penguin12.grid.surfsara.nl:2881/pnfs/grid.sara.nl/data/users/onno/README.txt response.code=207 response.reason=Multi-status socket.remote=145.38.218.162:49016 user-agent=curl/7.29.0 user.mapped=***** duration=6
There were no obvious errors. But the modification date of the file wasn't changed.
I tried the same with the creationdate, but that didn't work either.
400 Bad Request
or501 Not Implemented
?Kind regards, Onno