Email list hosting service & mailing list manager

ASGI, and further work related to www Amirouche Boubekki (15 Jun 2020 05:31 UTC)
Re: ASGI, and further work related to www John Cowan (15 Jun 2020 15:12 UTC)
Re: ASGI, and further work related to www Amirouche Boubekki (31 Jul 2020 11:05 UTC)
Re: ASGI, and further work related to www Lassi Kortela (31 Jul 2020 13:39 UTC)
Re: ASGI, and further work related to www John Cowan (02 Aug 2020 03:45 UTC)
Re: ASGI, and further work related to www Lassi Kortela (02 Aug 2020 06:13 UTC)
HTTP error codes Lassi Kortela (02 Aug 2020 06:21 UTC)
Re: HTTP error codes Amirouche Boubekki (02 Aug 2020 13:27 UTC)
Re: HTTP error codes John Cowan (03 Aug 2020 16:26 UTC)
Foreign errors are not necessarily errors Lassi Kortela (03 Aug 2020 16:35 UTC)
Re: Foreign errors are not necessarily errors John Cowan (03 Aug 2020 16:38 UTC)
Re: Foreign errors are not necessarily errors Lassi Kortela (03 Aug 2020 16:49 UTC)
Re: Foreign errors are not necessarily errors John Cowan (03 Aug 2020 16:53 UTC)
Re: HTTP error codes hga@xxxxxx (03 Aug 2020 16:47 UTC)
Re: HTTP error codes John Cowan (03 Aug 2020 17:04 UTC)
Re: HTTP error codes John Cowan (03 Aug 2020 17:07 UTC)
Re: ASGI, and further work related to www Amirouche Boubekki (02 Aug 2020 13:34 UTC)

Re: ASGI, and further work related to www Lassi Kortela 31 Jul 2020 13:39 UTC

> I will be working on an HTTP 1.1 request and response parser this
> week-end. I found a source of well tested http parsers in oss-fuzz
> project: https://github.com/google/oss-fuzz/tree/master/projects

Great, sounds good!

>>> 7) Start an SRFI about an HTTP client
>>
>> I have some ideas on that which I will try to post when I get some time for it.

IMHO the most important thing about HTTP clients is to have separate
serial and multiplexed clients. The serial one is much simpler. Unless
I'm mistaken, HTTP 1.1 is all serial, so the problem doesn't come up
here. But using the same API to access HTTP 1.1 and to access HTTP/2
serially would be useful.