On 28 Mar 2014 20:09:55 +0100, Chris Young wrote:
> I've just put a small patch in branch chris/http2 to enable libcurl to
> use HTTP 2.0 if it is the latest version.
>
> libcurl also needs building against nghttp2 for this to do anything
> (there is an equivalent patch in the toolchains chris/http2 branch)
>
> As it is still in draft I've put an option in to enable it, rather
> than it being enabled by default. Certainly Google's server - if not
> connecting over https - returns an error. Over https it works fine
> (and appears to have negotiated http2 to some extent), so I think it's
> probably just not up-to-date with the latest spec.
I've worked around this by only enabling HTTP2 support over https (as
it still fails with draft-12). This is all other web browsers
do anyway, we can revisit it if Google ever fix their server software.
If you turn on curl debug you can see it negotiating HTTP/2 in the
log. (good test server: https://nghttp2.org)
Chris
No comments:
Post a Comment