I can replicate this. The server side looks a bit like this (but with my local test setup, not Justas's): ``` 180714 07:08:11 16275 acc_Audit: http deny ligo@[2600:900:6:1301:5054:ff:fe0b:9cba] create /store/mc/hello_world.txt 180714 07:08:11 16275 ofs_open: ligo.7:136@hcc-briantest7 Unable to create /store/mc/hello_world.txt; permission denied 180714 07:08:11 16275 ligo.7:136@hcc-briantest7 XrootdResponse: sending err 3010: Unable to create /store/mc/hello_world.txt; permission denied 180714 07:08:11 16275 sysXrdHttp: XrdHttpReq::Error 180714 07:08:11 16275 ligo.7:136@hcc-briantest7 sysXrdHttp: PostProcessHTTPReq req: 4 reqstate: 0 180714 07:08:11 16275 ligo.7:136@hcc-briantest7 sysXrdHttp: Sending resp: 409 header len:44 180714 07:08:11 16275 sysXrdHttp: Sending 44 bytes 180714 07:08:11 16275 sysXrdHttp: Sending 10 bytes 180714 07:08:11 16275 sysXrdHttp: XrdHttpReq request ended. ``` So, internally, it is correctly reporting this as a permission denied: ``` 180714 07:08:11 16275 ligo.7:136@hcc-briantest7 XrootdResponse: sending err 3010: Unable to create /store/mc/hello_world.txt; permission denied ``` But the corresponding HTTP code is 409, which seems incorrect: ``` 180714 07:08:11 16275 ligo.7:136@hcc-briantest7 sysXrdHttp: Sending resp: 409 header len:44 ``` -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/766#issuecomment-405019800 ######################################################################## 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