-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
None
The 7 argument java.net.URI constructor encodes the parameters that are passed in. This is problematic because if an encoded query string is passed in, it will be encoded again (see AF-2908).
Elytron should not be encoding query strings or other parameters. It should just be using the request URI from Undertow without making any changes.
We should update ElytronHttpExchange#getRequestUri to use a StringBuilder instead of the 7 argument constructor.
- blocks
-
AF-2908 Asset with space in name cannot be opened in standalone editor
-
- Resolved
-
- causes
-
WFCORE-7210 Unescaped characters throw a NPE although allowed in settings
-
- Resolved
-
-
JBEAP-29571 [GSS](8.0.z) WFLY-20433 - Unescaped characters throw a NPE although allowed in settings
-
- QA In Progress
-
-
JBEAP-29572 [GSS](8.1.z) WFLY-20433 - Unescaped characters throw a NPE although allowed in settings
-
- Ready for QA
-
-
JBEAP-29573 [GSS](7.4.z) WFCORE-7210 - Unescaped characters throw a NPE although allowed in settings
-
- Ready for QA
-
- is cloned by
-
JBEAP-22822 (7.4.z) Update ElytronHttpExchange#getRequestURI to no longer use the 7 argument URI constructor
-
- Closed
-
- is incorporated by
-
WFCORE-5731 Upgrade Elytron Web to 1.10.1.Final
-
- Closed
-
- is triggering
-
ELYWEB-253 Add a test case for path encoding during FORM auth redirects
-
- Resolved
-