I made this particular tweak because Guile 2.2’s HTTP/1.1 client
requests were getting back an HTTP/2 response from a podcast
server, and choking. (The use of Google’s URL was just an example
to show the format of the HTTP response header.) Let’s drop the
patch for now. I’ll try disabling i
http/2 is a substantially different protocol, it will take
considerable effort to support it, guile's client should only be
offering http/1.1 to the server.
On Tue, 31 Mar 2020 at 15:49, Derek Upham wrote:
>
> Companies like Google now respond to HTTP requests with HTTP 2.
> For example:
>
> cu
The HTTP client code is aware of and handles strong and weak etags
as quoted strings (matching the spec), and strong etags as
unquoted strings (which don’t match the spec, but which some
servers send anyway). Some servers also violate the spec by
returning *weak* tags as unquoted strings. Thi
Companies like Google now respond to HTTP requests with HTTP 2.
For example:
curl --silent --head https://www.google.com
returns the first line
HTTP/2 200
The Guile HTTP client code expects a “HTTP/x.y” structure, and
treats this as an error. This patch recognizes and handles
“HTTP/2” on
Hi!
A small patch, fixing the use of IPv6 addresses for the built in HTTP
server. Also a really minor documentation fix.
--
hugo
>From d801c2975fe5fab8bc9bd5dc2f1d5b88a120cd46 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Hugo=20H=C3=B6rnquist?=
Date: Tue, 31 Mar 2020 15:04:50 +0200
Subject: [PATCH 1
