On Thu, May 5, 2016 at 1:29 PM, tomask79 <[email protected]> wrote:
> Hi Martin, > > REDIRECT_TO_BUFFER and by<Request> is meant > > "ILinkListener-content-contractDetailTabbedPanel-contractDetailTabbedPanel-panel-documentContentBusinessPanelsContainer-documentContentBusinessPanels-1-contractDetailClientDocumentBusinessPanel-revisionsPanel-table-body-rows-1-cells-2-cell-linkPropertyColumn.a&tabId=DlXvqFmLq9NbuPUcEk74 > HTTP/1.1" 302 333" > Is the <Request> always the same, i.e. the component path and the additional request parameters (e.g. tabId) are exactly the same for all redirects ? When REDIRECT_TO_BUFFER is used Wicket renders the page and stores the byte[] in a special Map in the Application. When a request comes Wicket uses its sessionId and request url as a composite key and checks whether there is a stored response for it in the Map. If there is stored result then there is no further processing and the byte[] is immediately written down in the response. If there is no stored byte[] then Wicket renders the page. If the original/requested url is the same as the one returned by RequestCycle.urlFor(new RenderPageRequestHandler(thePageInstance)) then the byte[] is written to the http response. If the url differs even in a single character then the byte[] is stored in the Map and a new redirect is made. The logic is in WebPageRenderer#respond(RequestCycle), but this is IMO the most complex code in Wicket. The final outcome depends on several variables (render strategy, is ajax, redirect strategy, original vs. current page url, etc.). > > thank you in advance for any hint where to look or what to check... > > T. > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Too-many-302-redirects-with-1-5-8-Wicket-tp4674532p4674565.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
