-
Bug
-
Resolution: Done
-
Critical
-
None
-
None
-
None
- causes
-
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
-
-
JBEAP-30947 [GSS](7.4.z) UNDERTOW-2609 - Previous fixes in the handling of decoded characters in query requests reflect in getQueryString of APIs
-
- New
-
-
JBEAP-28138 url-charset="MS949" does not work in AJP listener
-
- Verified
-
-
JBEAP-21293 [GSS](7.4.z) UNDERTOW-2312 - Unescaped characters in URL from client does not work correctly when allowed for HTTP and HTTPS listeners
-
- Verified
-
-
JBEAP-30316 [GSS](7.4.z) UNDERTOW-2555 - AJP Redirect with unescaped characters in URL is not encoded
-
- Resolved
-
-
JBEAP-30317 [GSS](8.1.z) UNDERTOW-2555 - AJP Redirect with unescaped characters in URL is not encoded
-
- Resolved
-
-
JBEAP-30605 [GSS](8.0.z) UNDERTOW-2555 - AJP Redirect with unescaped characters in URL is not encoded
-
- Resolved
-
-
JBEAP-15994 [GSS](7.2.z) Unescaped characters in URL from client does not work correctly when allowed for HTTP and HTTPS listeners
-
- 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
-
-
JBEAP-30945 [GSS](8.1.z) UNDERTOW-2609 - Previous fixes in the handling of decoded characters in query requests reflect in getQueryString of APIs
-
- Open
-
-
UNDERTOW-2609 Previous fixes in the handling of decoded characters in query requests reflect in getQueryString of APIs
-
- Coding In Progress
-
- is cloned by
-
JBEAP-25232 [GSS](8.0.z) UNDERTOW-2312 - Unescaped characters in URL from client does not work correctly when allowed for HTTP and HTTPS listeners
-
- Verified
-
- is incorporated by
-
WFCORE-6958 Upgrade Undertow to 2.3.16.Final
-
- Resolved
-