Disabling /console redirect to management port

[graham.johnson]

Wildfly's Undertow extension redirects /console/... URL requests (on port 8080/8443) to /console on port 9990.  Unfortunately, the web app that I am attempting to port to Wildfly already makes heavy use of /console/... URLs, and this redirect is preventing all those URLs from working.

As a temporary workaround I have installed a modified version of the wildfly-undertow-8.1.0-Final.jar (in the org.wildfly.extension.undertow:main module), with the part of org.wildfly.extension.undertow.HostAdd that adds org.wildfly.extension.undertow.ConsoleRedirectService (and the ServiceController for it) commented out, but I need a permanent solution (other than updating all our URLs, which is not really viable).

Is there any way (configuration, CLI, MBean operation, etc.) to disable/remove/stop ConsoleRedirectService to prevent this redirect from happening?  I can't see anything in the code that points to an obvious way to configure or disable it, but maybe there is a way to cause this specific service to be stopped?

I'm not sure of the purpose of this redirect other than to reduce confusion for people trying to use the management console without specifying the management port in the URL.  Will anything important break if the redirect is disabled?

- Graham Johnson

[jaikiran]

Hi Graham,

I don't fully understand the question. Do you mean that you have disabled the default welcome-content application that gets deployed at root ( / ) context and instead deployed your own web application to that context and then your application has resource URLs with the /console path prefix and WildFly redirects those URLs to 9990 port? If you have disabled the welcome-content application, then I wouldn't expect the redirect to be done. In other words, I would expect the redirect to be disabled too. Isn't that happening?

[jaikiran]

Just to add to that reply, to disable the welcome-content application, all you have to do is:

To disable it, remove "welcome-content" handler for location / in undertow subsystem

[ctomc]

That looks like an oversight on our side.

Can you create jira for this WildFly - JBoss Issue Tracker

[graham.johnson]

To disable it, remove "welcome-content" handler for location / in undertow subsystem

Thank you for the response.  I was not aware of and had not disabled the welcome content <location>, but removing that had no effect on the console redirect.  I suspect since my webapp's context root is /, it fully overrides the welcome content handler (and I would expect/hope, if that were not the case, that it would warn if two things are set up to handle /).

[graham.johnson]

Thank you for confirming there is not an existing mechanism to disable the redirect.

JIRA issue created: [WFLY-3918] Cannot disable ConsoleRedirectService - JBoss Issue Tracker

[sejanick]

Hi, is this fix something that is still in development?