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
..
admin	Renamed users:no-owner to users as main user fixture	2022-09-02 10:08:37 +01:00
content	Changed Content API caching to public	2022-09-26 14:54:50 +08:00