-
-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle trailing /
in routes
#369
Comments
IIRC Dream sticks to the RFCs in treating these differently, as, IIRC, |
Maybe we could introduce a small new addition to the Dream path syntax to handle an optional trailing slash, eg |
I was working on middleware for a project and noticed "Router path access is being removed from the API."
Is there a way to handle this with the functions still available? |
I guess with |
Currently, one has to separately handle the presence/absence of trailing slashes, by having a route for
""
, and one for"/"
.I think it would be more intuitive if a trailing slash were automatically added, or removed, via redirects.
For the record, Go's
serveMux
does the former.The text was updated successfully, but these errors were encountered: