Uploaded image for project: 'Wicket'
  1. Wicket
  2. WICKET-4659

The default exception mapper is replying cacheable exceptional responses

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 6.0.0-beta2
    • Fix Version/s: 6.0.0
    • Component/s: wicket
    • Labels:
      None

      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.

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            pedrosans Pedro Santos
            Reporter:
            pedrosans Pedro Santos
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development