-
Bug
-
Resolution: Done
-
Major
-
None
-
None
This is a followup for JBEAP-15128. Current implementation doesn't handle a query part of the URI same way as for the URL path part, see here. This results into a situation that incorrect value is propagated in the access.log. See here:
127.0.0.1 - - [16/Aug/2018:16:50:01 +0200] "GET /helloworld/한글이름_test.html?param=íê¸ì´ë¦ _ahoy HTTP/1.1" 200 950
127.0.0.1 - - [16/Aug/2018:16:48:57 +0200] "GET /helloworld/한글이름_test.html?param=한글이름_ahoy HTTP/1.1" 200 950
Note: this is a regression against EAP7.1.0 where this worked well.
- clones
-
JBEAP-15257 [GSS](7.1.z) UNDERTOW-1399 - multibytes language in URL query part of request to ajp-listener is broken
- Closed
- 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