 |
 |
@abh3 commented on this pull request. > @@ -0,0 +1,15 @@ +In the case XrdHttp has been configured, it is important that the configuration contains at least one digest algorithm registered in the IANA database: https://www.iana.org/assignments/http-dig-alg/http-dig-alg.xhtml +Otherwise the user will get a 403 error for each checksum request they will do. + +Here is a table summarizing the IANA-compliant checksum names: + +| Digest algorithm | HTTP digest | Will be base64 encoded | +|------------------|-------------|------------------------| +| md5 | md5 | true | +| adler32 | adler32 | false | +| sha1 | sha | true | +| sha256 | sha-256 | true | +| sha512 | sha-512 | true | +| cksum | UNIXcksum | false | For xrootd checksum plugins the return value is always a hex-string and that implies for certain checksums like SHAxxx (which we don't have implementation for as of yet) the HTTP code would need to convert it to base64. Thus far, all script implementation do the same. Having a common format for all checksums is the "standard" for xroot but not for http. I will make that obvious in the documentation. I think the table already specifies when conversion is necessary. The only odd one is Unixcksum (a.k.a. cksum) which is supposed to be a dec-string. However, since you are removing from the table the conversion issue becomes moot. -- Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/pull/1950#discussion_r1145544092 You are receiving this because you commented. Message ID: <[log in to unmask]> ######################################################################## 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