Hazelcast/JDBConfig clustering issues caused by HTTP 302 response and unique wicket resource IDs

Description

Trying out 2.9 Beta2 with Hazelcast clustering I noticed that every UI request results with an HTTP 302 response and a unique ID appended to the URL.
when using a single instance this isn't that big of an issue, however when having multiple instances behind a load balancer this results with multiple redirects, which causes the UI to be unusable.(In most cases the browser will just give up).
In some cases this can also become an issue with a single instance behind a proxy.

Looking around I wasn't able to find the commit that added that change, but I'm guessing this was done as part of the wicket upgrade.

Anyone knows if this was this was done in response to a specific issue, or just as an artifact of the wicket upgrade?
Would it be possible to change this behavior back to something that resembles 2.8 (eg HTTP 200 and non unique IDs)?

Thanks,
Ami.

Environment

None

Status

Assignee

Niels Charlier

Reporter

Niels Charlier

Triage

None

Fix versions

Affects versions

None

Components

Priority

Medium
Configure