Hi,

This was first reported to EOS (https://its.cern.ch/jira/browse/EOS-5203) but they told me it was an xrood issue.

ARC clients (for historical reasons) use the full URI in HTTP requests by default. This fails on EOS with 404:

[dcameron@lxplus722] ~> arccp -d DEBUG https://eosatlas.cern.ch/eos/atlas/atlasdatadisk/rucio/data18_13TeV/ff/ff/HIST_HLTMON.14686823._000075.pool.root.1 /tmp/dcameron/

...

DEBUG: > GET https://eosatlas.cern.ch/eos/atlas/atlasdatadisk/rucio/data18_13TeV/ff/ff/HIST_HLTMON.14686823._000075.pool.root.1 HTTP/1.1
Host: eosatlas.cern.ch:443
Connection: keep-alive
user-agent: ARC
DEBUG: No security processing/check requested for 'incoming'
DEBUG: < HTTP/1.1 404 NOT_FOUND
DEBUG: < Connection: Keep-Alive
DEBUG: < Content-Length: 3846
DEBUG: < Content-Type: text/html
DEBUG: < Date: Mon, 11 Apr 2022 06:44:33 GMT

Although the client behaviour is not really correct, RFC 7230 states that the server must support it:

To allow for transition to the absolute-form for all requests in some
future version of HTTP, a server MUST accept the absolute-form in
requests, even though HTTP/1.1 clients will only send them in
requests to proxies.

Cheers,
David

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1675", "url": "https://github.com/xrootd/xrootd/issues/1675", "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