-
Bug
-
Resolution: Done
-
Major
-
7.1.0.CR3
We receive a 400 response code if using UTF-8 characters for a request, due to this check:
This was introduced in UNDERTOW-1101. We want to understand why it is necessary for the CVE/CWE regarding request smuggling, but this ticket is to at least make this check optional as it goes against the URL_ENCODING UndertowOption when set to UTF-8 (default).
- clones
-
WFLY-9724 Undertow does not allow UTF-8 characters in URLs
- Closed
- duplicates
-
JBEAP-13393 [GSS](7.1.z) Allow special characters in HTTP request
- Closed
- is caused by
-
UNDERTOW-1185 Undertow does not allow UTF-8 characters in URLs
- Resolved
- is cloned by
-
JBEAP-13711 (7.0.z) Undertow does not allow UTF-8 characters in URLs
- Resolved
- is incorporated by
-
JBEAP-13744 [GSS](7.1.z) Upgrade undertow from 1.4.18.Final to 1.4.18.SP1
- Closed
- relates to
-
JBEAP-13751 [GSS](7.1.z) UNDERTOW-1221 - url-charset="MS949" did not work in ajp-listener
- Closed