From: Tristan Colgate <tcolgate@gmail.com>
To: Derek Upham <derek_upham@mailfence.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: [Patch] Support HTTP/2 in HTTP client
Date: Tue, 31 Mar 2020 16:00:54 +0100 [thread overview]
Message-ID: <CAPGZSG+GG4DrF-VgJ4neHb+H2ivcr4vKO9WvsCmEGLr+f+vyaQ@mail.gmail.com> (raw)
In-Reply-To: <87v9mkoab3.fsf@priss.frightenedpiglet.com>
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 <derek_upham@mailfence.com> wrote:
>
> 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 input and output. HTTP version numbers don’t
> proliferate quickly, so the code uses a brute force approach for
> now.
>
>
> Derek
>
> --
> Derek Upham
> derek_upham@mailfence.com
--
Tristan Colgate-McFarlane
----
"You can get all your daily vitamins from 52 pints of guiness, and a
glass of milk"
next prev parent reply other threads:[~2020-03-31 15:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 14:42 [Patch] Support HTTP/2 in HTTP client Derek Upham
2020-03-31 15:00 ` Tristan Colgate [this message]
2020-04-01 1:21 ` Derek Upham
2020-04-01 7:24 ` Tristan Colgate
2020-04-07 14:39 ` Derek Upham
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPGZSG+GG4DrF-VgJ4neHb+H2ivcr4vKO9WvsCmEGLr+f+vyaQ@mail.gmail.com \
--to=tcolgate@gmail.com \
--cc=derek_upham@mailfence.com \
--cc=guile-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).