intarweb/tests, branch intarweb-2.xAdvanced HTTP library to make building HTTP clients and servers convenient.
https://code.more-magic.net/intarweb/atom?h=intarweb-2.x2024-01-11T12:59:39ZCorrected Range and Content-Range header handling2024-01-11T12:59:39ZBilly Browndruidofluhn@gmail.com2023-12-21T17:07:00Zurn:sha1:b9683af2da882d542208a15d67d8040bab8fa5c2
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>
Fix tests with CHICKEN 5.0.22019-05-05T09:30:31ZPeter Bexpeter@more-magic.net2019-05-05T09:30:31Zurn:sha1:41d734f1c09581b16ae3bf97a67482d1ee37557c
Keywords can't be (ab)used as identifier anymore, so we can't bind
expression: with let-syntax. Instead, simply use the plain symbol.
The intarweb tests don't actually use srfi-18; drop the dependency2018-09-23T09:13:11ZPeter Bexpeter@more-magic.net2018-09-23T09:13:11Zurn:sha1:dd01f37c43ba8df952cc0f5fd0176691ada1592bInitial CHICKEN 5 port of intarweb 1.72018-06-22T20:22:24ZPeter Bexpeter@more-magic.net2018-06-22T20:22:24Zurn:sha1:90a1f7d47525cfffe928e9a89becf622bd85a8a1