-
Bug
-
Resolution: Done
-
Major
-
1.4.20.Final
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).
- causes
-
WFLY-9724 Undertow does not allow UTF-8 characters in URLs
- Closed
-
JBEAP-13710 [GSS](7.1.z) UNDERTOW-1185 - Undertow does not allow UTF-8 characters in URLs
- Closed
- duplicates
-
UNDERTOW-1256 Allow special characters in HTTP request
- Resolved
- relates to
-
WFLY-10929 Unescaped characters in URL from client does not work correctly when allowed for HTTP and HTTPS listeners
- 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