Doing more investigations I found that the problem is gathering the
extended browser info. Omitting that, BrowserInfoPage is stateless.
Sorry for the noise.
Regards
Alberto
On Thu, 2019-02-28 at 11:06 +0100, Alberto Brosich wrote:
> On Thu, 2019-02-28 at 01:50 -0800, Bas Gooren wrote:
> > Hi!
On Thu, 2019-02-28 at 01:50 -0800, Bas Gooren wrote:
> Hi!
>
> We have many stateless pages in our apps (public-facing, indexed, e-
> commerce websites), and use the default render strategy provided by
> wicket.
> When a page is stateless, wicket does not redirect.
>
> Are you sure your pages are
Hi!
We have many stateless pages in our apps (public-facing, indexed,
e-commerce websites), and use the default render strategy provided by
wicket.
When a page is stateless, wicket does not redirect.
Are you sure your pages are stateless?
Met vriendelijke groet,
Kind regards,
Bas Gooren
Op
Hello,
I didn't find any useful information about that in the documentation.
For some reasons (e.g. search engine bots or clients unable to follow
redirects) on some pages I would like to have an http 200 response. By
default Wicket uses REDIRECT_TO_BUFFER render strategy that send a 302
redire
