Could you try the same test using xroot protocol to see where the problem
really lies?
On Fri, 26 May 2023, ccaffy wrote:
> Interesting :)
>
> When I issued a HEAD request with a `Want-Digest: adler32` header on a file that does not exist, I properly get 404 Not Found Error.
>
> ```
> $ curl -H 'Want-Digest: sha-512' -I https://something.cern.ch:1096/tmp/non-empty-dir/does_not_exist.txt
> HTTP/1.1 404 Not Found
> Connection: Close
> Server: XrootD/v5.2.0-99-osghotfix...687
> Content-Length: 0
> ```
> But if I do a GET with a 'Want-Digest: sha-512' header on a file that does not exist:
>
> ```
> $ curl -H 'Want-Digest: sha-512' -X GET https://something.cern.ch:1096/tmp/non-empty-dir/does_not_exist.txt
> HTTP/1.1 500 Internal Server Error
> Connection: Close
> Server: XrootD/v5.2.0-99-osghotfix...687
> Content-Length: 51
>
> Underlying filesystem failed to calculate checksum.
> ```
>
>
>
> --
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/2018
> 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/2018/1565219989@github.com>
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/xrootd/xrootd/issues/2018#issuecomment-1565219989",
"url": "https://github.com/xrootd/xrootd/issues/2018#issuecomment-1565219989",
"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
