Then this may be an issue. If the current behaviour is OK for FTS but not
for DIRAC then we can't just simply change the behaviour to suit DIRAC as
it may break FTS. So, more investigation is needed here. Mind you that
reading the HTTP spec either code should be handled but it appears that
409 is the preferable one in this particular case (your intepretation of
the the may vary https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html).
Andy
On Mon, 28 Mar 2022, sfayer wrote:
> I'm not really sure: I suspect the answer is "5.0.0 and FTS is relying on the implicit directory creation so it doesn't hit the mkdir bug": I'm sure we would have seen it somewhere in production if it did affect FTS (the transfer system I'm having trouble with is an older/simpler DIRAC one that isn't FTS based).
>
> Regards,
> Simon
>
>
> --
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/1663#issuecomment-1080644161
> You are receiving this because you are subscribed to this thread.
>
> Message ID: ***@***.***>
—
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/1663/1081064350@github.com>
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/xrootd/xrootd/issues/1663#issuecomment-1081064350",
"url": "https://github.com/xrootd/xrootd/issues/1663#issuecomment-1081064350",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://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
