You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Mike (JIRA)" <ji...@apache.org> on 2014/08/29 18:00:54 UTC
[jira] [Created] (WICKET-5689) Nested Redirects and
REDIRECT_TO_BUFFER
Mike created WICKET-5689:
----------------------------
Summary: Nested Redirects and REDIRECT_TO_BUFFER
Key: WICKET-5689
URL: https://issues.apache.org/jira/browse/WICKET-5689
Project: Wicket
Issue Type: Bug
Affects Versions: 1.5.11
Environment: Windows 7, tomcat 7.0.47
Reporter: Mike
When the render strategy is REDIRECT_TO_BUFFER, redirects cannot be nested. After the second redirect, Wicket renders the buffered first page in preference to the second page. The relevant code is in WebPageRenderer.respond:
if (bufferedResponse != null)
{
logger.warn("The Buffered response should be handled by BufferedResponseRequestHandler");
// if there is saved response for this URL render it
bufferedResponse.writeTo((WebResponse)requestCycle.getResponse());
}
The attached quickstart demonstrates the issue. Simply navigate to the home page. The observed behavior is that Page1 is displayed, but I expect Page2 to be displayed.
I can work around the issue by calling WebApplication.getAndRemoveBufferedResponse() to clear the render buffer, but I am uneasy with this solution since it seems like I am playing with Wicket internals; albeit the function is public.
--
This message was sent by Atlassian JIRA
(v6.2#6252)