HTTP management interface switched

[elenderik]

While migrating WildFly 8.1.0.Final to 12.0.0.Final I stumbled on an odd behaviour of HTTP management interface (HMI).

Lets say I first start WildFly 12.0.0 and login into HMI. All is well (I see newer version of HMI).

Now lets say I start WildFly 8.1.0 and login into HMI. I see the HMI as it was under 12.0.0, but the core runtime etc is 8.1.0 (like it should be).

It goes the other way around also.

Lets say I first start WildFly 8.1.0 and login into HMI. All is well (I see older version of HMI).

Now lets say I start WildFly 12.0.0 and login into HMI. I see the HMI as it was under 8.1.0, but the core runtime etc is 12.0.0 (like it should be).

I tested these two cases separately under new Windows user, server was started in standalone.

I am out of thoughts with this one at the moment..

[dlofthouse]

I am assuming it is the admin console you are seeing from the different versions - it sounds as though it is just the web browser is caching the admin console previously downloaded.

If you are likely to be switching between the two often you may want to bind the management interfaces to different ports so the browser does not see them as the same.  From the perspective of a web browser it is not expected the same host / port combination would relate to different server instances.

[elenderik]

Yes, so it was - thanks, Darran, for the explanation.