Daniel Stenberg wrote:

> A modern curl version (built with OpenSSL) outputs a line like this in the verbose output to help users figure it out:
>
> * SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256

With 'curl -v https://www.ssllabs.com/ssltest/viewMyClient.html', I
also get the same:

  * ALPN, offering h2
  * ALPN, offering http/1.1
  ...
  * SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
  * ALPN, server did not agree to a protocol

Not sure I understand why the ALPN "fails" in libcurl (Win-10/MSVC,
OpenSSL/1.1.0). This "Application Layer Protocol Negotiation" works
fine in my Google Chrome:
  Application Layer Protocol Negotiation Yes h2 spdy/3.1 http/1.1

Is building with 'USE_NGHTTP2' required for this feature to work?

The page:
  https://en.wikipedia.org/wiki/Application-Layer_Protocol_Negotiation

says "It is used by HTTP/2". It doesn't says "HTTP/2" is required.
So I'm confused.

-- 
--gv
-------------------------------------------------------------------
List admin: https://cool.haxx.se/list/listinfo/curl-users
FAQ:        https://curl.haxx.se/docs/faq.html
Etiquette:  https://curl.haxx.se/mail/etiquette.html