Print

Print

Thanks for the update, Andy.

I might have a different opinion on when it's appropriate for the server to return an error, but you're right about the client having to handle error cases.

However, for me, these are more philosophical points.

The core problem underlying this issue is quite specific: xrootd currently returns a 500 status code if a client issues a GET request with Want-Digest: sha-512,sha-256;q=0.8,sha;q=0.6,md5;q=0.4,adler32;q=0.2.

In essence, dCache is asking for checksums, calculated with any algorithm it supports. dCache and xrootd implement a common subset of algorithms: at least ADLER32 and MD5. Therefore, (theoretically) xrootd should always be able to answer such a query.

—
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/1707/1127222525@github.com>

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