On Fri, 28 Mar 2014, Chris Young wrote:

> I notice with Firefox etc, Google's homepage just redirects to the secure
> version, so it's odd we get a 400 here rather than a 302 redirect.

Yes, I'm not sure why that is. But if you do http2 on the https site, you'll
see a 400 returned as well - only over http2 instead. I can see that with a
plain:

  $ curl -v --http2 https://www.google.com/

> If it isn't talking plain text HTTP2, then it ought to be ignoring the
> Upgrade: header anyway?

Yes, but since we get the 400 over http2 as well I think it is because
something else...

> I found another plain text http2 problem after I posted that. On the
> nghttp2 test server libcurl gets stuck requesting data. Again, the easy
> test is with the curl command line tool: curl -v --http2
> http://106.186.112.116/

Which nghttp2 version is that with? I tried with the git master version just
now and curl does just fine against that server!

-- 
  / daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html