Open
Bug 638574
Opened 15 years ago
Updated 3 years ago
Prevent cache-related false positive/negative results on CSP demo site
Categories
(Core :: DOM: Core & HTML, enhancement, P5)
Core
DOM: Core & HTML
Tracking
()
NEW
People
(Reporter: briansmith, Unassigned)
Details
We did not notice that one of the CSP demos broke recently because the browser had cached some resources that caused the broken demo to function correctly. We should ensure that we are getting accurate results. E.g. make all resources in the demo uncacheable using Cache-Control headers, or add a note to the main CSP demo site that instructs the user to clear the cache and refresh.
Comment 1•15 years ago
|
||
Good call. I'm hacking the demo pages at the moment anyway (adding a policy-uri and policy-uri-fails test) so I can add cache-control: no-cache to all those resources.
Comment 2•15 years ago
|
||
Or put an appropriate Vary header on the resources?
Comment 3•15 years ago
|
||
This should be fixed. I put:
Header unset ETag
Header set Cache-Control "max-age=0, no-cache, no-store, must-revalidate"
Header set Pragma "no-cache"
Header set Expires "Tue, 01 Jan 1980 06:00:00 GMT"
in the .htaccess for all of the tests and subresources. Brian, since you filed this bug do you want to test the demo and close the bug if it seems right to you?
http://people.mozilla.org/~bsterne/content-security-policy/demo.cgi
Updated•14 years ago
|
Component: Security → DOM: Core & HTML
QA Contact: toolkit → general
Comment 4•8 years ago
|
||
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046
Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5.
If you have questions, please contact :mdaly.
Priority: -- → P5
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•