You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I needed a test WebDAV server, so I decided to attempt to use the package, but it appears that this software does not implement the range header properly. The RFC https://tools.ietf.org/html/rfc2616#section-14.35 states that the ranges is inclusive:
The last-byte-pos value gives the
byte-offset of the last byte in the range; that is, the byte
positions specified are inclusive. Byte offsets start at zero.
In the request, this does not appear to be the case. This is a log from a request:
Thanks for the testing and clear reporting. I'm not actively working on this project though, to be honest I only ever created it as a test tool for a WebDAV client I used to work on.
I'm more than happy to merge and release any patches though if you're interested in fixing the issue!
I needed a test WebDAV server, so I decided to attempt to use the package, but it appears that this software does not implement the range header properly. The RFC https://tools.ietf.org/html/rfc2616#section-14.35 states that the ranges is inclusive:
In the request, this does not appear to be the case. This is a log from a request:
The request requests 20 bytes, (21 - 2 + 1), but as you can see, the reply only includes 19 bytes.
It also looks like it does not honor range, as if I manually do the request:
A lot more data is included than the specified range:
The data was a simple file that contained the above string, and zero padded to 1MB.
The text was updated successfully, but these errors were encountered: