Why does JBoss EAP 7 return "400 Bad Request" response when sending unescaped characters in the request URL after updating to EAP 7.0.6+?

Solution Verified - Updated -

Issue

  • JBoss EAP 7 returns "400 Bad Request" response when sending unescaped characters (raw UTF-8 characters like Â) in the request URL after updating to JBoss EAP 7.0 CP6 or later.
  • JBoss EAP 7 returns "400 Bad Request" response when sending unescaped characters (raw UTF-8 characters like Â) in the query string and path parameters of the request after updating to JBoss EAP 7.0 CP9 or later.
  • We recently updated to JBoss EAP 7.0 CP6 or later and we are having the same issue to https://access.redhat.com/solutions/2891171 / https://access.redhat.com/solutions/3181201.
  • On EAP 7, what is the equivalent to EAP 6's tomcat.util.http.parser.HttpParser.requestTargetAllow property?

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP) 7

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In