Lines Matching refs:HTTP

1 HTTP/2 with curl
4 [HTTP/2 Spec](https://www.rfc-editor.org/rfc/rfc7540.txt)
17 parts. The reason for this is that HTTP/2 is much more complex at that layer
18 than HTTP/1.1 (which we implement on our own) and that nghttp2 is an already
28 upgrading to HTTP/2.
32 use HTTP/2 at once over http://
39 option that will cause libcurl to fail if not possible to use HTTP/2.
42 HTTP/2 for HTTPS but stick to 1.1 by default for plain old HTTP connections.
44 ALPN is the TLS extension that HTTP/2 is expected to use.
52 Starting in 7.43.0, libcurl fully supports HTTP/2 multiplexing, which is the
58 attempt to re-use existing HTTP/2 connections and just add a new stream over
61 While libcurl sets up a connection to an HTTP server there is a period during
73 We hide HTTP/2's binary nature and convert received HTTP/2 traffic to headers
74 in HTTP 1.1 style. This allows applications to work unmodified.
79 curl offers the `--http2` command line option to enable use of HTTP/2.
82 HTTP/2 without HTTP/1.1 Upgrade.
84 Since 7.47.0, the curl tool enables HTTP/2 by default for HTTPS connections.
89 The command line tool does not support HTTP/2 server push. It supports
92 HTTP Alternative Services
95 Alt-Svc is an extension with a corresponding frame (ALTSVC) in HTTP/2 that