Thanks, that does indeed clarify things. It seems my mind was not yet fully wrapped around the different layers, but this makes a lot of sense (as expected 😉 ).

So if I understand correctly, to do things in sequence via XrdHttp, we need some changes:

• HTTP PUT by definition means "replace the resource such that I can get it back with GET", which is also how it is implemented.
• However, this currently translates into a single request (open with kXR_mkpath | kXR_open_wrto | kXR_delete), which basically is an "all-in-one" request to the file system. That's true to the definition of PUT, but does not allow granular application of privileges.
• This should be separated into doing things step by step (check existence, if so, delete, then create, then write to the file) to allow granular privileges to be applied.

That seems very reasonable, but requires more code changes than I expected (which is surely not a bad thing, doing things right often requires more changes than expected). However, it means that I (currently, and in the near future) lack the time to go through with it — if somebody else steps up earlier than I can come back to it, I can surely support (e.g. share the implementation of the part @bbockelm suggested which I have already finished, but which needs to be done in-sync with the other changes to really have an effect).

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <xrootd/xrootd/issues/1655/1097185277@github.com>

Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1