Path and query parameters are not decoded properly UndertowOptions#ALLOW_ENCODED_SLASH in JBoss EAP 7.4

Solution Unverified - Updated -


path& query parameters are not decoded properly due to flag/meaning switch of flag

This means that not only parts of code had wrong value hardcoded, but UndertowOptions#ALLOW_ENCODED_SLASH had opposite meaning.

Using a predicate path-prefix('/foo') -> rewrite('/bar${remaining}') for a request path that already has some url-encoded segments will result in rewritten path being different than intended.

For example, a request to /foo/hello%2Fworld will end up being /bar/hello%252Fworld instead of the expected /bar/hello%2Fworld

I noticed this problem on WildFly in a JAX-RS method that must handle such urlencoded values in a @PathParam


  • Red Hat Enterprise Application Platform (EAP) 7.4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content