Allow caching some API responses that change rarely #1560
Merged
+30
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allow the browser to cache some API responses for endpoints that change very very rarely. These in particular are used by the new PI and letting the browser cache them for a bit will make the initial PI load faster when users are coming in and out of the PI (the PI doesn't reload these when it moves between pages).
We cache the site documents and dictionaries for a day. Project pickersets for an hour.
Sandbox: https://www.pgdp.org/~cpeel/c.branch/cache-some-api-responses/
Testing is making sure the
Cache-Controlheader is included in the response, eg: