Naz 4528cba1b9 Changed Content API caching to public ... refs https://github.com/TryGhost/Toolbox/issues/410 - Private cache control was preventing browser or shared caches from storing Content APIs response. The type of data served through the Content API is very much of a "public" nature, so should be cacheable. - Right now the 'max-age' value of 'cache-control' header is hardcoded to '0', without 'must-revalidate' value, to allow browsers to cache content slightly more aggressively. In the future the 'max-age' value will most-likely become configurable to allow even more aggressive HTTP caching.		2022-09-26 14:54:50 +08:00
..
__snapshots__	Changed Content API caching to public	2022-09-26 14:54:50 +08:00
authors.test.js	Changed Content API caching to public	2022-09-26 14:54:50 +08:00
key_authentication.test.js	Changed Content API caching to public	2022-09-26 14:54:50 +08:00
newsletters.test.js	Converted Ghost repo into a monorepo	2022-07-20 16:41:05 +02:00
offers.test.js	Converted Ghost repo into a monorepo	2022-07-20 16:41:05 +02:00
pages.test.js	Fixed Content API posts/pages e2e tests	2022-09-13 15:05:53 +01:00
posts.test.js	Fixed Content API posts/pages e2e tests	2022-09-13 15:05:53 +01:00
settings.test.js	Converted Ghost repo into a monorepo	2022-07-20 16:41:05 +02:00
tags.test.js	Changed Content API caching to public	2022-09-26 14:54:50 +08:00
tiers.test.js	Converted Ghost repo into a monorepo	2022-07-20 16:41:05 +02:00
utils.js	Converted Ghost repo into a monorepo	2022-07-20 16:41:05 +02:00