Uploaded image for project: 'Repose'
  1. REP-5617

Log Message When Adding Header to Response (after it is committed)

    Details

    • Type: Story
    • Status: Resolved (View workflow)
    • Priority: Medium
    • Resolution: Done
    • Affects versions: None
    • Fix versions: 8.6.3.0
    • Components: None
    • Labels:
      None
    • Sprint:
      Sprint 148, Sprint 149
    • Story Points:
      3
    • Capitalizable:
      True

      Description

      When adding a header to the response, the wrapper doesn't check to see if the response has already been committed back to the user. Once committed we should not modify response any more.

      We should throw an IllegalStateException if someone tries to add a header after the wrapper has been committed.

      Acceptance Criteria:

      • A filter can not add a header to a wrapper after it's been committed.
        • That is, don't add it to the collection of headers in the response wrapper if it's been committed.
      • A message is logged when a header is added to the response wrapper after it's been committed as not having failed.

        Attachments

          Activity

            People

            • Assignee:
              wdschei Bill Scheidegger
              Reporter:
              adrian.george Adrian George
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: