That's what I found when I tried to put this weighted-checksum want-digest value.

$ cat xrd_http.cfg | grep chksum
xrootd.chksum crc32 adler32

[xrootddev@xrootd-ccaffy-dev01 http_server_certificate_tests]$ curl -I -H "Want-Digest: sha-512,sha-256;q=0.8,sha;q=0.6,md5;q=0.4,adler32;q=0.2"  -L https://xrootd-ccaffy-dev01.cern.ch:1096/tmp/bigfile_5M_copy
HTTP/1.1 200 OK
Connection: Keep-Alive
Server: XrootD/v5.2.0-99-osghotfix...687
Content-Length: 15
Digest: crc32=06c3f8e8

I asked the adler32 checksum in the list, but you see, I get a CRC32 one because it is the first configured in the server config list.

That's because the algorithm looking for the checksum to run from the user list does strict string comparison --> no algorithm is found and the first configured one is computed.

With my new fix (not pushed yet), it works as expected:

[xrootddev@xrootd-ccaffy-dev01 http_server_certificate_tests]$ curl -I -H "Want-Digest: sha-512,sha-256;q=0.8,sha;q=0.6,md5;q=0.4,adler32;q=0.2"  -L https://xrootd-ccaffy-dev01.cern.ch:1096/tmp/bigfile_5M_copy
HTTP/1.1 200 OK
Connection: Keep-Alive
Server: XrootD/v5.2.0-99-osghotfix...687
Content-Length: 15
Digest: adler32=2204040b
Accept-Ranges: byte

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

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