Hi

I just had a play around with the new draft HTTP2 support in
Curl/libcurl. For the most part it works great, however Google's
web server GFE/2.0 does not seem to like it when attempting to connect
over a non-secure connection. This is easily reproduced with the
following command, which produces the output attached: curl -v --http2
http://www.google.co.uk

As you can see, GFE returns HTTP error 400. When connecting over a
secure connection, however, it works as expected.

I assume this is because Google isn't up-to-date with the latest draft
spec? Can anything be done with libcurl to workaround the error? If
it was just Google it wouldn't be a problem, but
http://www.blogspot.co.uk uses the same server software and there's no
secure alternative on that.

Regards
Chris

('plain' encoding is not supported, stored as-is)

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
(end of MIME multipart message)