urlencoding issue with non-ASCII chars in request-uri header #614
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.
Hello,
this is the fix for the issue #613.
The issue
The problem was that the route
/κκκκ
was not accessible. After some debugging, I found out that the complete url was urlencoded and then compared to the url of the route./%CE%BA%CE%BA%CE%BA%CE%BA
is not/κκκκ
.When you urldecode
/%CE%BA%CE%BA%CE%BA%CE%BA
you get/\xce\xba\xce\xba\xce\xba\xce\xba/
(UTF-8) which is equals to/κκκκ
.So why is the url urlencoded?
A Stackoverflow post brought to my attention that the browser urlencodes special chars and passes them using the
request-uri
header.The solution
I changed
$this->setUrl(new Url($this->getFirstHeader(['unencoded-url', 'request-uri'])));
to
so that the header will now be correctly urldecoded.
~ Marius