diff options
| author | Billy Brown <druidofluhn@gmail.com> | 2023-12-21 17:07:00 +0000 |
|---|---|---|
| committer | Peter Bex <peter@more-magic.net> | 2024-01-11 13:59:39 +0100 |
| commit | b9683af2da882d542208a15d67d8040bab8fa5c2 (patch) | |
| tree | 947497195eb439a0a22e4839f9adcb952c4b579c /benchmarks/unparsers.scm | |
| parent | b2632661807a99fc7c3e610e8bd1b04c68b869c5 (diff) | |
| download | intarweb-2.1.0.tar.gz | |
Corrected Range and Content-Range header handling2.1.0
Corrected the handling of the Range request header and the Content-
Range response header. They now have separate parsers, to match the
standard, and the content-range unparser is now correctly named.
The Range header can be in one of three forms:
Range: bytes=<start>-<end>
Range: bytes=<start>-
Range: bytes=-<end>
The Content-Range header can be in one of three forms:
Content-Range: bytes <start>-<end>/<size>
Content-Range: bytes <start>-<end>/*
Content-Range: bytes */<size>
The unit tests were updated to reflect the changes.
Signed-off-by: Peter Bex <peter@more-magic.net>
Diffstat (limited to 'benchmarks/unparsers.scm')
0 files changed, 0 insertions, 0 deletions