Hi,
I would expect it to hit the container. Debuggin and testing on a test
environment works and hits it. Unfortunatelly there is no way to
definitely proove that the error in question hits it to. I do know that
the onConfigure is not hit. I don't have access to the access logs.
Is there a way that the user uses a proxy that disables the response
headers we set for caching?
Thanks!
On 05/11/13 14:22, Martin Grigorov wrote:
Hi,
It looks like the page is loaded from the browser/proxy cache.
Can you verify that the web container is hit ? E.g. check its access logs
On Tue, Nov 5, 2013 at 4:05 PM, Artur Kronenberg <
artur.kronenb...@openmarket.com> wrote:
Hi,
I have a rather odd problem with a page of mine. The design is that the
model on the page gets a flag set that indicates that the send button has
been clicked (so the user doesn't send multiple times by clicking it
vigurously over and over again).
The problem now is that on browser back, the model is still created and
the page can't be used.
I overwrote the onConfigure method to set up my model correctly and
everything works just fine. However there seems to be cases where the
onConfigure method is not called?
Does anyone know of those cases? Can it have anything to do with the user
using a proxy? A weird browser thing?
We set the response headers to:
Expires: -1
Pragma: no-cache
Cache-Control: no-cache, max-age=0, must-revalidate, no-store
This seems to be a very odd issue that I can not reproduce locally at all
(I used to be able to by hitting the back button so I am guessing this is
where things happen, but overwriting onConfigure fixed it for most cases).
Thanks!
Artur
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
