RESOLVED FIXED 140312
Cache-control should be set only on api/runs 
https://bugs.webkit.org/show_bug.cgi?id=140312
Summary Cache-control should be set only on api/runs
Ryosuke Niwa
Reported 2015-01-09 14:32:41 PST
Some JSON APIs such as api/analysis-tasks can get outdated pretty quickly as they could be modified by the user on demand. Since the only JSON that takes a long time to generate is ones returned by api/runs, just set cache-control in that script instead.
Attachments
Fixes the bug (3.72 KB, patch)
2015-01-09 14:37 PST, Ryosuke Niwa 		kling: review+
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Ryosuke Niwa
Comment 1 2015-01-09 14:37:16 PST
Created attachment 244372 [details] Fixes the bug
Andreas Kling
Comment 2 2015-01-09 14:38:10 PST
Comment on attachment 244372 [details] Fixes the bug View in context: https://bugs.webkit.org/attachment.cgi?id=244372&action=review r=me > Websites/perf.webkit.org/public/api/runs.php:18 > +// FIXME: We should support revalication as well as caching results in the server side. Typo, revalidation.
Ryosuke Niwa
Comment 3 2015-01-09 14:39:30 PST
Committed r178208: <http://trac.webkit.org/changeset/178208>
Note You need to log in before you can comment on or make changes to this bug.