Wildfly 18.0.1.Final has changed the redirection behaviour for context root. Any way to reset it.

[Sandip Shaw]

I am upgrading from wildfly-16 to wildfly 18.0.1.Final and seeing the behavior change for request redirection for context root. For Widfly 16, any request http:/localhost:8080/myapp (myapp is context root) will be redirected to http:/localhost:8080/myapp/ (adding a forward slash at the end) but this behavior has been modified in Wildfly 18.0.1.Final. Instead of redirect status code (304), response is returning 200 status code. Is there any way to restore the old behavior that is redirecting request if forward slash is not available at end of url(for context root).

The similar  issue has been asked at below jboss developer forum:

https://developer.jboss.org/thread/280821

[Sandip Shaw]

On Tuesday, March 3, 2020 at 3:19:39 PM UTC+5:30, Sandip Shaw wrote:

I am upgrading from wildfly-16 to wildfly 18.0.1.Final and seeing the behavior change for request redirection for context root. For Widfly 16, any request http:/localhost:8080/myapp (myapp is context root) will be redirected to http:/localhost:8080/myapp/ (adding a forward slash at the end) but this behavior has been modified in Wildfly 18.0.1.Final. Instead of redirect status code (302), response is returning 200 status code. Is there any way to restore the old behavior that is redirecting request if forward slash is not available at end of url(for context root).

[Sandip Shaw]

It is broken due to undertow subsystem upgrade in Wildfly 18.0.0.Final. It is fixed in latest undertow 2.0.30.Final (issues.redhat.com/browse/UNDERTOW-1637) but wildfly has still not upgraded to 2.0.30.Final. We have to wait for issues.redhat.com/browse/WFCORE-4825 to be done so changes are still not in 19.X.Beta.

[James Perkins]

I would say there is a good chance 2.0.30.Final will make it into WildFly 19. I won't guarantee it yet, but I have a feeling it will make it :)

--

James R. Perkins