Okay, I figured it out. In that particular chunk of code I was
calling out to Curl to do the heavy lifting: “(run/port (curl
--silent --head ,source-url))”. Curl negotiates HTTP/2 and dumps
the header information:
HTTP/2 200
date: Tue, 07 Apr 2020 14:22:37 GMT
content-type: audio/mpeg
I'm not sure why a server would give you a http2 response if you
didn't ask for one (or atleast suggest you could accept one), in the
tls ALPN. If it happened on a non-tls request, I'm even more confused.
Note that curl, without extra cli options, will negotiate http2, so
you need to make sure th
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
