Branch: refs/heads/master
Home: https://github.com/xrootd/xrootd
Commit: 0a8ec92cf32afe6dce7ef0e3a83cb2f6ab60454b
https://github.com/xrootd/xrootd/commit/0a8ec92cf32afe6dce7ef0e3a83cb2f6ab60454b
Author: Brian Bockelman <[log in to unmask]>
Date: 2023-02-22 (Wed, 22 Feb 2023)
Changed paths:
M src/XrdHttp/XrdHttpReq.cc
Log Message:
-----------
Denote Accept-Ranges in HEAD response
Some clients (particularly, the golang library used by stashcp) will
probe for byte range support by issuing a HEAD request and looking
for the standard `Accept-Ranges` header in the response. Set this
header in XrdHttp as we do support byte ranges.
Commit: d83e15507e673b35ff5f5620a342cf3608f4b3bb
https://github.com/xrootd/xrootd/commit/d83e15507e673b35ff5f5620a342cf3608f4b3bb
Author: Brian Bockelman <[log in to unmask]>
Date: 2023-02-22 (Wed, 22 Feb 2023)
Changed paths:
M src/XrdHttp/XrdHttpReq.cc
Log Message:
-----------
Bugfix: Correct response for single byte range
If an open-ended byte range is requested by the client:
```
Range: bytes=1234-
```
then the HTTP server was setting the end of the range to `-1`. In
this case, once the file is opened, the end of the range should be
set to `filesize - 1` (note ranges are inclusive of the end byte,
meaning it looks like it's off-by-one -- that's just how the HTTP
spec works).
Without this, a single open-ended byte range request would fail.
Compare: https://github.com/xrootd/xrootd/compare/7fa97760395d...d83e15507e67
########################################################################
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
