David Pedersen

There isn't and I don't think that use case can ever work. The solution we are thinking about here is to make the full path available in the response extensions...

Nope, and like I wrote above I don't think there is a way.

Yes there are work arounds. You can probably also add configuration to your middleware or only add it in some places, if you wanna authorized based on the matched path.

We half fixed it. I think we could still make the full matched path available in response extensions so people can use it for logging (suggested here https://github.com/tokio-rs/axum/issues/1441#issuecomment-1272158039)

How is that related to this bug? But to answer your question you probably want [`MethodRouter::or`](https://docs.rs/axum/latest/axum/routing/method_routing/fn.on.html). For example `.route("/", on(MethodFilter::GET | MethodFilter::POST, handler))`

You can do `.route_with_tsr("/test", get(handler).post(handler))`

I'm not sure what changed but I can't reproduce this ```rust #[debug_handler] async fn handler(_: Path

I've started the work in https://github.com/tokio-rs/axum/pull/1882 but it's currently blocked by tower-http getting updated. That is blocked by figuring out how to implement the (de?)compression middleware.

An update on where we're at with regards to hyper 1.0 support: - Sean is planning to ship hyper 1.0 on November 15th 2023. This is super exciting! I can't...

This was fixed in https://github.com/tokio-rs/axum/pull/1882. See https://github.com/tokio-rs/axum/milestone/6 for things left to do before axum 0.7 can be shipped.