New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 788627 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Returning false from UrlDataSource::AllowCaching() doesn't fully disable caching

Project Member Reported by msimoni...@opera.com, Nov 27 2017

Issue description

Chrome Version: 64.0.3278.1
OS: all

What steps will reproduce the problem?
(1) Implement a UrlDataSource with AllowCaching() that returns false.
(2) Access the resources generated by the UrlDataSource multiple times (e.g. by setting it as a CSS background on an element multiple times).

What is the expected result?
It is expected that the renderer will fetch the resource every time, instead the resource is cached.

What happens instead?
The resource is cached in the renderer.

This can be fixed by changing URLDataManagerBackend::GetHeaders to set the "Cache-Control" header to "no-store" instead of "no-cache" as it is now (I can submit a patch).
 

Sign in to add a comment