That's right, but seems like this redirect doesn't arrive to browser, not even sure it comes to IIS. I looked at the IIS logs, it says error 400. The same redirection with the old server (WL10, Wicket 1.5.10) through the same IIS is OK.
I even just tried to deploy the older war on the WL12, it fails on same problem. WL12 seems to cause something wrong... Do you have an idea of a possible cause ? (non standard behaviour ? something else ?) Something else to try ? Thanks in advance... --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
