 |
 |
Hi Andy, I looked into this a bit more and it seems this change in behaviour was accepted for v5.0.0-rc2 (https://github.com/xrootd/xrootd/pull/1164), but v5.0.0-rc3 added the more specific "kXR_ItExists" error code (https://github.com/xrootd/xrootd/commit/cece19ddc8f6bebe5eb2768549ca474714f65cc9) meaning it doesn't hit that specific case in the original patch any more. I don't think this will cause any problems with FTS: other storage servers also return 405 in this case and don't run into FTS issues. While I agree that 409 would made more sense, it's reserved for a different case by the webdav RFC (for when a user tries to make a directory before the parent exists): I don't know why it's this way around but 405 is what they picked for the mkcol "already exists" case (https://datatracker.ietf.org/doc/html/rfc4918#section-9.3.1). Regards, Simon -- Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/1663#issuecomment-1081111071 You are receiving this because you are subscribed to this thread. Message ID: <[log in to unmask]> ######################################################################## 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