Hi, Are you using X-Forwarded headers sent by your balancer?
You can to override this method in you WicketApplication class to try to debug the redirect: @Override protected WebResponse newWebResponse(final WebRequest webRequest, final HttpServletResponse httpServletResponse) { return new ServletWebResponse((ServletWebRequest) webRequest, httpServletResponse) { @Override public String encodeRedirectURL(CharSequence url) { String encodedUrl = super.encodeRedirectURL(url); if (webRequest.getUrl().getProtocol() == "https") { //https } return encodedUrl; } }; } On Fri, Sep 1, 2017 at 10:20 AM, tomask79 <tomas.klou...@embedit.cz> wrote: > After some investigation this seems to be happening > when HeapUsage at the affected node is almost 100%... > > Memory statistics by org.apache.wicket.protocol. > http.requests.RequestLogger > few moments before the mentioned redirect looping: > > > > I'm confused by the following: > > 1) Why wicket things that URL is changing when it's not!(response handler > is > RequestSettingRequestHandler)... > > 2) What triggers these requests...It has to be Wicket, because > RequestSettingRequestHandler is response. > > Thanks for any kind of hint or help. > > > > -- > Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum- > f1842947.html > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Marcel Barbosa Pinto 55 11 98255 8288