[WICKET-4659] The default exception mapper is replying cacheable exceptional responses

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 6.0.0-beta2
• Fix Version/s: 6.0.0
• Component/s: wicket
• Assignee: Pedro Santos
• Reporter: Pedro Santos
• Created: 17/Jul/12 07:27
• Updated: 17/Aug/23 17:00
• Resolved: 17/Jul/12 09:43

Description

The problem is that some common URLs in the application like to a page instance are responding the cached exception page rather than hitting the server for the page instance being requested. It happens because at some moment in the past a exception page were replied and cached for a request in this URL.

Issue Links

• relates to: WICKET-7067 DefaultExceptionMapper should not set disableCaching for WebSocketResponse