Implemented allow_encoded_slashes aka handling of 2%F as part of the PAT... #1060
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The implementation is similar to the Apache2 AllowEncodedSlashes directive (see http://httpd.apache.org/docs/2.2/mod/core.html).
RFC 3875 specifies that a server MAY reject encoded slashes, and implementing this feature
should really be done on the HTTP server level.
The problem here is that HTTP::Server::Simple and its use of CGI seems to be quite hard coded
from a Dancer point-of-view. Anyhow, the result passes all tests on Linux.
Feel free to pull the patch ... sorry for not choosing an appropriate branch on my side.
Any suggestions/corrections are highly welcome.