vbrandl/actix-request-identifier

Middleware for actix-web to associate an ID with each request

actix-request-identifier's Issues

no default features for actix-web

If/when the actix-web dependency is updated to v3, the dependency in Cargo.toml should ideally be:

- actix-web = "3.0.2"
+ actix-web = { version = "3.0.2", default-features = false }

Don't replace a passed x-request-id

When using Envoy or another reverse proxy/ingress gateway, they already add an x-request-id header to the request arriving at actix so this middleware needs to take and keep this value instead of replacing it.

In case of no value, the middleware needs to generate one.

Can you add an example code to fix it?