Wicket
  1. Wicket
  2. WICKET-5304

AbstractResource should check for error code first before for modifications

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 6.9.1
    • Fix Version/s: 6.10.0, 7.0.0-M1
    • Component/s: wicket
    • Labels:
      None

      Description

      Since org.apache.wicket.request.resource.AbstractResource#setResponseHeaders() gives a chance to the application to set custom headers it should first check for error and status codes set and then check for modifications (Not Modified).
      Because now one needs to reset the modification time of the resource if she wants to set error or status code.

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Martin Grigorov
            Reporter:
            Martin Grigorov
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development