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 produc
On Fri, 28 Mar 2014 22:38:25 +0100 (CET), Daniel Stenberg wrote:
> 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.
I notice with Firefox etc, Google's homepa
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
On Mon, 31 Mar 2014 08:35:44 +0200 (CEST), Daniel Stenberg wibbled on for an
age:
> On Fri, 28 Mar 2014, Chris Young wrote:
>
> >> $ curl -v --http2 https://www.google.com/
> >
> > I'm getting a 302 here
> I get a different server but I did this:
Hi
I notice libcurl 7.37.0 uses if_nametoindex() in lib/url.c.
There are defines to check for both net/if.h and IFNAMSIZ. However,
here I have both of those, but still don't have if_nametoindex().
Is there any chance a test for if_nametoindex can be added to
configure instead?
Chris
--
Hi
There are some problems building curl/libcurl with more recent AmigaOS
releases, which I've been meaning to raise for a while. A more random
problem has prompted me to post this now.
There is an issue with conflicting "struct timeval" definitions with
certain OS releases and C libraries, depe
On Tue, 20 Jan 2015 09:06:28 +0100 (CET), Daniel Stenberg wrote:
> > It's easy enough to resolve this at the curl end, by casting the
> > potentially
> > errorneous calculation to a signed long (see attachment).
>
> I merged and pushed that one now.
Thanks.
> > The second issue, which is the
On Thu, 22 Jan 2015 23:46:59 +0100 (CET), Daniel Stenberg wrote:
> On Tue, 20 Jan 2015, Chris Young wrote:
>
> > I've only built here for AmigaOS 4 (which *requires* that code to be
> > removed) and AmigaOS 3 against clib2 (which doesn't need it). Against
>