Tower middleware and utilities for HTTP clients and servers.
More information about this crate can be found in the crate documentation.
Tower HTTP contains lots of middleware that are generally useful when building HTTP servers and clients. Some of the highlights are:
Traceadds high level logging of requests and responses. Supports both regular HTTP requests as well as gRPC.CompressionandDecompressionto compress/decompress response bodies.FollowRedirectto automatically follow redirection responses.
See the docs for the complete list of middleware.
Middleware uses the http crate as the HTTP interface so they're compatible with any library or framework that also uses http. For example hyper.
The middleware were originally extracted from one of @EmbarkStudios internal projects.
The examples folder contains various examples of how to use Tower HTTP:
- warp-key-value-store: A key/value store with an HTTP API built with warp.
- tonic-key-value-store: A key/value store with a gRPC API and client built with tonic.
- axum-key-value-store: A key/value store with an HTTP API built with axum.
tower-http's MSRV is 1.66.
If you're new to tower its guides might help. In the tower-http repo we also
have a number of examples showing how to put everything together.
You're also welcome to ask in the #tower Discord channel or open an
issue with your question.
🎈 Thanks for your help improving the project! We are so happy to have you! We have a contributing guide to help you get involved in the Tower HTTP project.
This project is licensed under the MIT license.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in Tower HTTP by you, shall be licensed as MIT, without any additional terms or conditions.
