You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a problem related to the fix of this issue.
That fix only solved the problem for the plus sign "+" but there are similar issues with some other characters as "%".
Is it possible to avoid the double decoding for preventing a similar issue with other characters?
Expected behavior
All of the double decoding related issues should be solved with the fix for the related issue
Minimal reproducible example
In this case with the "%" character, it's encoded as "%25" in the query parameter, but the double decoding in the Location constructor leads to an exception. As an example:
Location l = new Location("https://example.com?param=%25HF")
After decoding once, "%25HF" becomes "%HF". Since "%HF" is not a valid url-encoded pattern, it throws an exception.
Versions
Vaadin / Flow version: 14.8.0 (but probably also remains in the latest version)
The text was updated successfully, but these errors were encountered:
Description of the bug
This is a problem related to the fix of this issue.
That fix only solved the problem for the plus sign "+" but there are similar issues with some other characters as "%".
Is it possible to avoid the double decoding for preventing a similar issue with other characters?
Expected behavior
All of the double decoding related issues should be solved with the fix for the related issue
Minimal reproducible example
In this case with the "%" character, it's encoded as "%25" in the query parameter, but the double decoding in the Location constructor leads to an exception. As an example:
Location l = new Location("https://example.com?param=%25HF")
After decoding once, "%25HF" becomes "%HF". Since "%HF" is not a valid url-encoded pattern, it throws an exception.
Versions
The text was updated successfully, but these errors were encountered: