intarweb, branch 2.1.0

Corrected Range and Content-Range header handling

2024-01-11T12:59:39Z

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=- Range: bytes=- Range: bytes=- The Content-Range header can be in one of three forms: Content-Range: bytes -/ Content-Range: bytes -/* Content-Range: bytes */ The unit tests were updated to reflect the changes. Signed-off-by: Peter Bex

Add 2.0.3 release

2023-09-07T11:04:21Z

Use string-downcase instead of string-downcase! in http-name->symbol

2023-09-07T11:01:42Z

Unlike the srfi-1 linear updating procedures with exclamation marks, in srfi-13, the side-effecting operations do *not* necessarily return the string. They just mutate it in-place. This fixes #1826, so that it will work with utf CHICKEN (upcoming C6).

Publish 2.0.2

2021-09-13T14:02:11Z

Export rfc1123-time->string

2021-09-13T13:59:35Z

This is a procedure that can be used by users of this egg which need the string representation of the Date header (for signing purposes, for example, like the S3 egg needs for the AWS signature) The problem is that we don't really want to bake in "letlocale" in all other programs, but contain this horrid complexity in intarweb.

Release version 2.0.1

2019-05-05T09:31:12Z

Fix tests with CHICKEN 5.0.2

2019-05-05T09:30:31Z

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 dependency

2018-09-23T09:13:11Z

Use -d0 to improve performance a tiny bit

2018-08-12T14:44:40Z

Add missing release-info file

2018-06-22T20:46:50Z