First, the Digest response header copies the supplied Want-Digest
request header value. A request with:
Want-Digest: MD5,ADLER32
would yield a response like:
Digest: MD5,ADLER32=<md5-value>
where the correct response would be:
Digest: MD5=<md5-value>
Second, the method that calculates whether the response should be
encoded in hexadecimal or base64 expects an algorithm name, but is given
the Want-Digest request header value. If the client makes a request with:
Want-Digest: MD5, ADLER32
then the response is incorrectly encoded using hexadecimal.
You can view, comment on, or merge this pull request online at:
https://github.com/xrootd/xrootd/pull/1002
-- Commit Summary --
* Fix two problems with RFC-3230 handling in xrootd:
-- File Changes --
M src/XrdHttp/XrdHttpReq.cc (18)
M src/XrdHttp/XrdHttpReq.hh (6)
-- Patch Links --
https://github.com/xrootd/xrootd/pull/1002.patch
https://github.com/xrootd/xrootd/pull/1002.diff
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/xrootd/xrootd/pull/1002
########################################################################
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
