cURL / Mailing Lists / curl-users / Single Mail

curl-users

Re: Curl and HTTP/2

From: Daniel Stenberg <daniel_at_haxx.se>
Date: Sun, 24 Aug 2014 23:32:44 +0200 (CEST)

On Sat, 23 Aug 2014, Bisera Milosheska wrote:

Please don't top-post, it makes reading longer thread really hard.

> I tried the git clone on another machine(which may have had the standard
> curl package previously installed with apt-get), because I didn’t want to
> mess up something on the machine I was working on. That was the response I
> got after downloading curl from the repository on the other machine. So my
> explanation is that I was getting the answer from the older version of curl.

And you built everything from source fine and installed it in a separata
install path it and you _know_ it was that curl + libcurl that was used?

> Good note about the OpenSSL version, I am also very confused now. Despite
> the fact that curl is build with OpenSSL/1.0.1f, which is not supposed to
> support ALPN, h2-14 is still negotiated when TLS is used on the server side.

But you're not telling us all the details. Did it even use ALPN or was this
perhaps one of those servers that are perfectly happy with negotating http2
with NPN? NPN support exists already in earlier OpenSSL versions and libcurl
will use both or either, depending on what support that exist in the TLS
library.

> However, when I start the sever with the —no-tls option and I request the
> same resource only via http, I get this response:
>
> [id=1] [ 8.131] send SETTINGS frame <length=6, flags=0x00, stream_id=0>
> (niv=1)
> [SETTINGS_MAX_CONCURRENT_STREAMS(0x03):100]
> [id=1] [ 8.132] closed
>
> Do you have any idea why this might be so?

Is this using 7.38.0-DEV ? What exactly does curl do? Can you use curl's
--trace option and log from its side?

> Also, I am trying for quite some time already to find a way to upgrade the
> OpenSSL version and I cannot succeed. I have tried to get it from different
> resources too and it is not recognised. 1.0.1f is the version which ‘apt-get
> installs’ and ’sudo apt-get update’, ’sudo apt-get upgrade’ and ’sudo
> apt-get dist-upgrade’ don’t help either.

Is your distribution even providing newer OpenSSL packages like that? I use
Debian unstable and OpenSSL/1.0.1i is what it provides == not new enough for
ALPN.

For ALPN support, I just get OpenSSL from their git repository and build my
own version and install in a custom prefix. Works fine.

-- 
  / daniel.haxx.se

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-users
FAQ: http://curl.haxx.se/docs/faq.html
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2014-08-24