feat(session): add rustls (actix#342)

actix-session/CHANGES.md

@@ -2,6 +2,7 @@
 
 ## Unreleased
 
+- Added support for using `rustls` in `actix-session` instead of `native-tls`
 - Remove `redis-actor-session` crate feature (and, therefore, the `actix-redis` based storage backend).
 
 ## 0.9.0

actix-session/Cargo.toml

@@ -22,6 +22,7 @@ default = []
 cookie-session = []
 redis-rs-session = ["redis", "rand"]
 redis-rs-tls-session = ["redis-rs-session", "redis/tokio-native-tls-comp"]
+redis-rs-tls-session-rustls = ["redis-rs-session", "redis/tokio-rustls-comp"]
 
 [dependencies]
 actix-service = "2"

actix-session/README.md

@@ -116,6 +116,14 @@ By default, `actix-session` does not provide any storage backend to retrieve and
   actix-session = { version = "...", features = ["redis-rs-session", "redis-rs-tls-session"] }
   ```
 
+  If you instead prefer using `rustls`, use the `redis-rs-tls-session-rustls` feature flag:
+
+  ```toml
+  [dependencies]
+  # ...
+  actix-session = { version = "...", features = ["redis-rs-session", "redis-rs-tls-session-rustls"] }
+  ```
+
 You can implement your own session storage backend using the [`SessionStore`] trait.
 
 [`SessionStore`]: storage::SessionStore

actix-session/src/storage/redis_rs.rs

@@ -44,7 +44,7 @@ use crate::storage::{
 /// ```
 ///
 /// # TLS support
-/// Add the `redis-rs-tls-session` feature flag to enable TLS support. You can then establish a TLS
+/// Add the `redis-rs-tls-session` or `redis-rs-tls-session-rustls` feature flag to enable TLS support. You can then establish a TLS
 /// connection to Redis using the `rediss://` URL scheme:
 ///
 /// ```no_run