The current cache implementation uses request url as a key even when Cache-Control policy is private.
This might lead to leaking data from one user to another, creating security holes in an application.
I would expect it to cache based on request url + authorisation header in case the cache control policy is private, e.g. a hashed combination of these values
The current cache implementation uses request url as a key even when
Cache-Controlpolicy is private.This might lead to leaking data from one user to another, creating security holes in an application.
I would expect it to cache based on request url + authorisation header in case the cache control policy is private, e.g. a hashed combination of these values