nest and route behaviour

[ghost]

Bug Report

Version

v0.3.4

Platform

Windows 11 64 bit

Description

I have a GraphQL endpoint which I need to access from /graphql and /graphql/ with below code:

let app = Router::new().nest("/graphql", post(graphql_handler));

in previous version, both /graphql and /graphql/ work just fine pointing to the same graphql handler. after updating to 0.3 using route makes /graphql/ unreachable while nest makes /graphql unreachable. is this expected? I need /graphql/ because trunk proxy somehow put the last slash to the request.

[jplatte]

If you don't need any sub-routes of the form /graphql/foo and want both /graphql and /graphql/ to work without redirects, I think that would just be

Router::new()
    .route("/graphql", post(graphql_handler))
    .route("/graphql/", post(graphql_handler))

[davidpdrsn]

Yep thats correct.

By default axum will redirect to the route with/without trailing slash depending on which you've defined. So if you define /foo and request /foo/ axum will redirect to /foo, or vice versa. If you define both routes explicitly then no redirects will happen.

[ghost]

thank you for the quick answer