mirror of
https://github.com/actix/actix-web.git
synced 2024-12-24 09:00:34 +00:00
doc updates
This commit is contained in:
parent
1598e78de1
commit
97b149f321
1 changed files with 17 additions and 7 deletions
|
@ -1,6 +1,7 @@
|
|||
//! ETag header and `304 Not Modified` support for HTTP responses
|
||||
///
|
||||
/// The `EtagHasher` middleware generates RFC 7232 ETag headers for HTTP
|
||||
/// The `EtagHasher` middleware generates [RFC
|
||||
/// 7232](https://tools.ietf.org/html/rfc7232) ETag headers for HTTP
|
||||
/// responses, and checks the ETag for a response against those provided
|
||||
/// in the `If-None-Match` header of the request, if present. In the
|
||||
/// event of a match, instead of returning the original response, an
|
||||
|
@ -15,6 +16,13 @@
|
|||
/// body, but in return one avoids sending response bodies to requesters
|
||||
/// that already have the body content cached.
|
||||
///
|
||||
/// This approach is most useful for dynamically generated responses
|
||||
/// that don't correspond to a specific external resource (e.g. a
|
||||
/// file). For such external resources, it's better to generate ETags
|
||||
/// based on the inherent properties of the resource rather than by
|
||||
/// hashing the bytes of an HTTP response corresponding to its
|
||||
/// serialized representation as this middleware does.
|
||||
///
|
||||
/// An `EtagHasher` instance makes use of two functions, `hash` and
|
||||
/// `filter`. The `hash` function takes the bytes of the original
|
||||
/// response body as input and produces an ETag value. The `filter`
|
||||
|
@ -73,9 +81,6 @@ use middleware;
|
|||
|
||||
use std::marker::PhantomData;
|
||||
|
||||
/// `Middleware` for generating ETag headers and returning `304 Not Modified`
|
||||
/// responses upon receipt of a matching `If-None-Match` request header.
|
||||
|
||||
/// Can produce an ETag value from a byte slice. Per RFC 7232, **must only
|
||||
/// produce** bytes with hex values `21`, `23-7E`, or greater than or equal
|
||||
/// to `80`. Producing invalid bytes will result in a panic when the output
|
||||
|
@ -137,9 +142,14 @@ impl<S> RequestFilter<S> for DefaultFilter {
|
|||
}
|
||||
}
|
||||
|
||||
/// The middleware struct. Contains a Hasher to compute ETag values for byte
|
||||
/// slices and a filter to determine whether ETag computation and checking
|
||||
/// should be applied to a particular (request, response) pair.
|
||||
/// Middleware for [RFC 7232](https://tools.ietf.org/html/rfc7232) ETag
|
||||
/// generation and comparison.
|
||||
///
|
||||
/// The `EtagHasher` struct contains a Hasher to compute ETag values for
|
||||
/// byte slices and a Filter to determine whether ETag computation and
|
||||
/// checking should be applied to a particular (request, response)
|
||||
/// pair. Only response [Body](enum.Body.html)s of type `Binary` are
|
||||
/// supported; responses with other body types will be left unchanged.
|
||||
pub struct EtagHasher<S, H, F>
|
||||
where
|
||||
S: 'static,
|
||||
|
|
Loading…
Reference in a new issue