On Fri, 28 Mar 2014 23:45:36 +0100 (CET), Daniel Stenberg 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/
I'm getting a 302 here (well, after I disable the certificate checking): * Hostname was NOT found in DNS cache * Trying 173.194.41.146... * Connected to www.google.com (173.194.41.146) port 443 (#0) * SSLv3, TLS handshake, Client hello (1): * SSLv3, TLS handshake, Server hello (2): * NPN, negotiated HTTP1.1 [...] > GET / HTTP/1.1 > User-Agent: curl/7.36.0 > Host: www.google.com > Accept: */* > < HTTP/1.1 302 Found It's not doing http2 though. > Which nghttp2 version is that with? I tried with the git master version just > now and curl does just fine against that server! 0.3.2. Maybe it has been fixed since then? Hope so! Chris ------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
