[WICKET-5621] Store more information to/with BufferedWebResponse that survives multi-RequestCycle redirect

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 6.16.0
• Component/s: wicket
• Assignee: Unassigned
• Reporter: Hendy Irawan
• Created: 17/Jun/14 07:34
• Updated: 17/Jun/14 07:37

Description

From mgrigorov :

It seems org.apache.wicket.response.filter.ServerAndClientTimeFilter and the other similar filters lie because they use the current request cycle's begin time. The processing time when there is a buffered response should be quite small.

The reported time at the moment is not very useful.
It seems we need to store more information to/with BufferedWebResponse to be able to cover the requirements in this mail thread and WICKET-5129.

Original thread and use case: http://apache-wicket.1842946.n4.nabble.com/How-to-get-PageClass-from-BufferedResponseRequestHandler-And-how-to-quot-link-quot-related-requests-td4666247.html

Issue Links

• blocks: WICKET-5129 HttpsMapper Does Not Switch to SSL when there is no JSESSIONID Cookie
• links to: [wicket-user] How to get PageClass from BufferedResponseRequestHandler ? And how to "link" related requests?