2018-05-22 23:15:08 +02:00
---
2020-09-12 17:21:54 +02:00
title: HTTP/2
menu: docs_protocols
2018-05-22 23:15:08 +02:00
weight: 250
---
2022-03-07 14:40:36 +01:00
Actix Web will prefer HTTP/2 connections if the client signals support for it via [TLS ALPN][tlsalpn].
2018-05-22 23:15:08 +02:00
# Negotiation
2020-09-12 17:21:54 +02:00
<!-- TODO: use rustls example -->
2022-02-26 05:41:49 +01:00
2022-03-07 14:40:36 +01:00
When either of the `rustls` or `openssl` features are enabled, `HttpServer` provides the [bind_rustls][bindrustls] method and [bind_openssl][bindopenssl] methods, respectively.
2018-05-22 23:15:08 +02:00
```toml
[dependencies]
2019-12-28 17:37:19 +01:00
actix-web = { version = "{{< actix-version " actix-web " > }}", features = ["openssl"] }
2018-05-22 23:15:08 +02:00
openssl = { version = "0.10", features = ["v110"] }
```
2022-02-26 05:41:49 +01:00
2019-06-18 23:17:43 +02:00
{{< include-example example = "http2" file = "main.rs" section = "main" > }}
2018-05-22 23:15:08 +02:00
2022-03-07 14:40:36 +01:00
Upgrades to HTTP/2 described in [RFC §3.2][rfcsection32] are not supported. Starting HTTP/2 with prior knowledge is supported for both cleartext and TLS connections ([RFC §3.4][rfcsection34]) (when using the lower level `actix-http` service builders).
2018-05-22 23:15:08 +02:00
2019-06-25 05:36:32 +02:00
> Check out [examples/tls][examples] for a concrete example.
[rfcsection32]: https://http2.github.io/http2-spec/#rfc.section.3.2
[rfcsection34]: https://http2.github.io/http2-spec/#rfc.section.3.4
2022-03-07 14:40:36 +01:00
[bindrustls]: https://docs.rs/actix-web/4/actix_web/struct.HttpServer.html#method.bind_rustls
2022-03-06 00:55:35 +01:00
[bindopenssl]: https://docs.rs/actix-web/4/actix_web/struct.HttpServer.html#method.bind_openssl
2019-06-25 05:36:32 +02:00
[tlsalpn]: https://tools.ietf.org/html/rfc7301
2022-02-28 14:48:50 +01:00
[examples]: https://github.com/actix/examples/tree/master/https-tls/rustls