Page Versioning - F5 load balancer Monitoring

[Mihir Chhaya <mi...@gmail.com>]

Hello,

I have recently migrated my wicket app from 1.4 to 7.

Problem:
Page versioning is generating redirect loop for F5 load balancer monitoring.

Background:
We have F5 load balancer monitor running every few seconds to check 200 OK
from host/app/login for application availability monitoring. This worked
fine with 1.4 but, it is going into redirect loop after migration to Wicket
7 as 7 uses page versioning and host/app/login request from application
comes back with 302 Moved temporarily header since Wicket 7 is appending
page Id '?#' after login. 1.4 was also using page versioning but page Id
was not appended, and so F5 monitor was getting 200 OK from wicket.

In 1.4 I was using mountBookmarkablePage("login", Login.class).
In 7, I am using mountPage("/login", Login.class).

I understand that page versioning is due to the fact that the page is
stateful. But as we have modal window(password management - expired, will
expire soon type of functionality) and some Ajax links on the login page, I
can't make it stateless at this moment to avoid page versioning.

For now, I am using static jsp page (index.jsp) under WebContent without
any redirect to bring 200 OK to F5 load balancer monitor. I don't want 302
to be treated like '200 OK' as it could be returned for different reasons.

I tried setVersioned(false) but not luck; I assume this is due to the fact
that my page containing stateful components (ajax link, modal etc).

Knowing that I 'cannot' convert my login page to stateless at this moment,
is there any way I could still make F5 monitor work with login page? Has
anybody experienced similar situation before?

Thanks in advance,
-Mihir.

Re: Page Versioning - F5 load balancer Monitoring

[Mihir Chhaya <mi...@gmail.com>]

Thanks, Christoph. For now, I have created HealthCheck Stateless page in
place of jsp, and mounted as /health.

On Fri, Oct 30, 2015 at 3:59 AM, Christoph Läubrich <la...@googlemail.com>
wrote:

> You could check if you can configure F5 to accept 302 code as a valid life
> sign (maybe something like "don't follow redirects or such")
> If you just want to check that the webserver is there an wicket is running
> I would create a special CheckPage that is stateless and mounted unter a
> static path. You could even embedd some kind of statistic information in
> this page or return an error page if you detect some kind of problem in
> your app (e.g. DB down...).
>
>
> Am 30.10.2015 06:00, schrieb Mihir Chhaya:
>
>> Hello,
>>
>> I have recently migrated my wicket app from 1.4 to 7.
>>
>> Problem:
>> Page versioning is generating redirect loop for F5 load balancer
>> monitoring.
>>
>> Background:
>> We have F5 load balancer monitor running every few seconds to check 200 OK
>> from host/app/login for application availability monitoring. This worked
>> fine with 1.4 but, it is going into redirect loop after migration to
>> Wicket
>> 7 as 7 uses page versioning and host/app/login request from application
>> comes back with 302 Moved temporarily header since Wicket 7 is appending
>> page Id '?#' after login. 1.4 was also using page versioning but page Id
>> was not appended, and so F5 monitor was getting 200 OK from wicket.
>>
>> In 1.4 I was using mountBookmarkablePage("login", Login.class).
>> In 7, I am using mountPage("/login", Login.class).
>>
>> I understand that page versioning is due to the fact that the page is
>> stateful. But as we have modal window(password management - expired, will
>> expire soon type of functionality) and some Ajax links on the login page,
>> I
>> can't make it stateless at this moment to avoid page versioning.
>>
>> For now, I am using static jsp page (index.jsp) under WebContent without
>> any redirect to bring 200 OK to F5 load balancer monitor. I don't want 302
>> to be treated like '200 OK' as it could be returned for different reasons.
>>
>> I tried setVersioned(false) but not luck; I assume this is due to the fact
>> that my page containing stateful components (ajax link, modal etc).
>>
>> Knowing that I 'cannot' convert my login page to stateless at this moment,
>> is there any way I could still make F5 monitor work with login page? Has
>> anybody experienced similar situation before?
>>
>> Thanks in advance,
>> -Mihir.
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>

Re: Page Versioning - F5 load balancer Monitoring

[Christoph Läubrich <la...@googlemail.com>]

You could check if you can configure F5 to accept 302 code as a valid 
life sign (maybe something like "don't follow redirects or such")
If you just want to check that the webserver is there an wicket is 
running I would create a special CheckPage that is stateless and mounted 
unter a static path. You could even embedd some kind of statistic 
information in this page or return an error page if you detect some kind 
of problem in your app (e.g. DB down...).

Am 30.10.2015 06:00, schrieb Mihir Chhaya:
> Hello,
>
> I have recently migrated my wicket app from 1.4 to 7.
>
> Problem:
> Page versioning is generating redirect loop for F5 load balancer monitoring.
>
> Background:
> We have F5 load balancer monitor running every few seconds to check 200 OK
> from host/app/login for application availability monitoring. This worked
> fine with 1.4 but, it is going into redirect loop after migration to Wicket
> 7 as 7 uses page versioning and host/app/login request from application
> comes back with 302 Moved temporarily header since Wicket 7 is appending
> page Id '?#' after login. 1.4 was also using page versioning but page Id
> was not appended, and so F5 monitor was getting 200 OK from wicket.
>
> In 1.4 I was using mountBookmarkablePage("login", Login.class).
> In 7, I am using mountPage("/login", Login.class).
>
> I understand that page versioning is due to the fact that the page is
> stateful. But as we have modal window(password management - expired, will
> expire soon type of functionality) and some Ajax links on the login page, I
> can't make it stateless at this moment to avoid page versioning.
>
> For now, I am using static jsp page (index.jsp) under WebContent without
> any redirect to bring 200 OK to F5 load balancer monitor. I don't want 302
> to be treated like '200 OK' as it could be returned for different reasons.
>
> I tried setVersioned(false) but not luck; I assume this is due to the fact
> that my page containing stateful components (ajax link, modal etc).
>
> Knowing that I 'cannot' convert my login page to stateless at this moment,
> is there any way I could still make F5 monitor work with login page? Has
> anybody experienced similar situation before?
>
> Thanks in advance,
> -Mihir.
>
>    


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org