Actual Behavior

The cache key is currently generated based on the following details:

• hash algo
• request method
• URI
• request body

Expected Behavior

One should be able to customize this behaviour.

Example: Separate cache entry per authorization header.

Possible Solutions

Introduce a CacheKeyGenerator interface which would receive the request as a parameter.
It should be an optional parameter of the plugin, falling back to the current implementation.