Ooups, wrong handling, I mixed my aliases in previous email :-(
That was the answer to Sven about the browser requests.
Sorry
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail:
WL10 :
wanted URL : 302 to
;JSESSIONID= 302 to
?0 200 -> OK
WL12 :
wanted URL : 503 after 2-3 minutes
after i try with WL12, in the IIS logs, i find http 400
Check your browser network console, what URL is redirected to and whether the
following request succeeds.
Sven
>
> On 26.04.2019 at 10:58,wrote:
>
>
> That's right, but seems like this redirect doesn't arrive to browser, not
> even sure it comes to IIS. I
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
By adding the link your page becomes stateful.
So Wicket will issue a redirect to a second url with a number attached, e.g. ?1
You'll have to check what your url rewrite is doing to that redirect url.
Hope this helps
Sven
>
> On 25.04.2019 at 14:03,
Hi,
I am migrating an application using wicket and a network configuration a bit
weird, and i'm facing a unexpected behaviour.
The network configuration:
outside
|
IIS URL rewrite
|
Weblogic with Wicket app
The snippet :
I have simplified the app, so i reproduce the code on a quickstart-based
