On Fri, 28 Mar 2014, Chris Young wrote:
I assume this is because Google isn't up-to-date with the latest draft spec?
Google does not believe in doing plain-text http2 so I think this is on purpose. They will simply require https to speak http2.
That's basically the same situation like with SPDY.
Can anything be done with libcurl to workaround the error?
If it isn't just an oversight or just-not-implemented-yet on their part, there's nothing libcurl can do. The plain-text way to do http2 is to use Upgrade: exactly like that but it of course only works if the server then responds with an actual upgraded protocol...
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.
I assume you either won't speak http2 to that server or they'll start offering it over https...
-- / daniel.haxx.se ------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
