-
Notifications
You must be signed in to change notification settings - Fork 39
Add trailing_slash http route option #173
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
base: master
Are you sure you want to change the base?
Add trailing_slash http route option #173
Conversation
|
0f5c1f5
to
a4908c4
Compare
How Mojolicious behaves in the case? |
Can we stick with Mojo's behavior (without an option) and don't break existing users? If so, I would prefer to don't add the option to don't bloat the API. |
@Totktonada Mojo has an option - |
Mojo has
I doubt that I understand the motivation of the change good enough. Can we start from a description of your particular case and your particular problem? |
@Totktonada sure, let me try to describe the problem:
http server decodes In fact, it modifies In case of:
I agree, its correct. But not for encoded values. |
Wow. It is just a bug and should be fixed without any options. |
Please rebase with master branch. |
Add trailing_slash http route option.
trailing_slash
defines the trailing slash behavior for the route and as a result req:stash behaviour . The initial value is true.