Details

    • Type: Bug
    • Status: Resolved
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 2.0.0, 2.0.1, 2.1.0, 2.1.1, 2.1.2, 2.2.0, 2.2.1
    • Fix Version/s: 2.2.2
    • Component/s: Caching
    • Labels:
      None

      Description

      2.2.0 added feature to pass user attributes as headers.
      However, headers are not considered in cache key generation.
      This means two users' responses from a URL that was nuanced by identity information in headers will have the same cache key, and so User B could see the response cached for User A.

      This drew attention to inappropriate cross-user caching issues that have been present through the whole v2 series until v2.2.2.

        Attachments

          Issue links

            Activity

              People

              • Assignee:
                awp9 Andrew Petro
                Reporter:
                awp9 Andrew Petro
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: