-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
8.1.0.GA
-
None
-
False
-
-
False
-
-
-
-
-
-
-
When UndertowOptions.ALLOW_UNESCAPED_CHARACTERS is enabled, we want to follow that config as part of Undertow's internal contract when, for example, printing the request in the AccessLog.
This relates to UNDERTOW-2312 and other related issues, for a full list, please se linked issues.
The previous fixes are reflecting on the getQueryString implementation of apis such as Servlet, and this is causing malfunction for users that rely on frameworks that are build on top of those APIs.
For that reason, the previous fixes need to be carefully reviewed so that we don't create a regression in those Jiras while also amending the behavior of HttpServerExchange.getQueryString(), the method that is used by Undertow to reply to any request on the query string done via APIs such as HttpServletRequest.getQueryString(), and any related code that might have the same effect.
- clones
-
UNDERTOW-2609 Previous fixes in the handling of decoded characters in query requests reflect in getQueryString of APIs
-
- Coding In Progress
-
- is caused by
-
UNDERTOW-2312 multibytes language in URL request to http/https are broken in EAP access log.
-
- Closed
-
-
UNDERTOW-2555 AJP Redirect with unescaped characters in URL is not encoded
-
- Closed
-
-
UNDERTOW-2567 Decoding of query strings with unescaped characters does not work in HTTP2 upgrade
-
- Closed
-
- is cloned by
-
JBEAP-30946 [GSS](8.0.z) UNDERTOW-2609 - Previous fixes in the handling of decoded characters in query requests reflect in getQueryString of APIs
-
- New
-