Disable naive caching

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.

Environment

None

Assignee

Andrew Petro

Reporter

Andrew Petro

Labels

None

Estimated End Date

None

Components

Fix versions

Affects versions

Priority

Blocker
Configure