tower-request-id
| Crates.io | tower-request-id |
| lib.rs | tower-request-id |
| version | 0.3.0 |
| source | src |
| created_at | 2021-09-29 07:23:32.597794 |
| updated_at | 2023-12-02 10:41:35.897182 |
| description | A tower (hyper, axum, warp) service to add a unique id for every request |
| homepage | |
| repository | https://github.com/imbolc/tower-request-id |
| max_upload_size | |
| id | 457907 |
| size | 36,936 |
Imbolc (imbolc)
documentation
README
tower-request-id
A tiny tower (hyper, axum, warp etc) service to generate a random id for each incoming request.
Usage
After adding the [RequestIdLayer] into the axum middlewares the request id is available in
the [http::Request::extensions()]. For the tracing integration, please refer to the
logging example.
Contributing
We appreciate all kinds of contributions, thank you!
Note on README
Most of the readme is automatically copied from the crate documentation by cargo-sync-readme. This way the readme is always in sync with the docs and examples are tested.
So if you find a part of the readme you'd like to change between <!-- cargo-sync-readme start -->
and <!-- cargo-sync-readme end --> markers, don't edit README.md directly, but rather change
the documentation on top of src/lib.rs and then synchronize the readme with:
cargo sync-readme
(make sure the cargo command is installed):
cargo install cargo-sync-readme
If you have rusty-hook installed the changes will apply automatically on commit.
License
This project is licensed under the MIT license.