Best practice for custom page renderer

[Alberto Brosich]

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
redirect first.

Which is the best practice for use ONE_PASS_RENDER strategy?

Is it reasonable to adopt ONE_PASS_RENDER for all stateless pages or is
it better to change the render strategy only for specific pages?

Is setPageRendererProvider() the good place where to handle that?

For example:

setPageRendererProvider( new IPageRendererProvider() {

  @Override
  public PageRenderer apply(RenderPageRequestHandler handler) {
                                
    return new WebPageRenderer(handler) {
      
      @Override
      protected boolean isOnePassRender() {
                                
        IRequestablePage page =
getRenderPageRequestHandler().getPage();

        return page.isPageStateless() ||
page instanceof BrowserInfoPage || super.isOnePassRender();
        }
     };
  }
});

I' working with wicket version 8.3.0.

Best regards

Alberto


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