cessda-bitbucket-importer
commented
3 years ago Original comment by Matthew Morris (GitHub: matthew-morris-cessda).
Hi Sigit,
The first issue I can see is that the HTTP cache-control header is set to max-age=126230400000, public, which means that browsers, as well as any other cache, will cache the response for 4,000 years.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control
It would be better to use a more reasonable max-age parameter, as well as using the no-cache directive. Using no-cache will cause clients to always recheck with the server if a newer resource is avaliable.
A side note is that the json is served with the incorrect text/html mime type, it should use application/json.
Original report on BitBucket by sigit nugraha.
Hi @Joshocan & @matthew-morris-cessda
There is a blocker issue #296, which mentioned that the recently published CV sometimes does not appear on the publication side. I think this is related to the cache in the Google Cloud side, which does the caching for the publicly accessible static files. The published CVs are stored in static JSON files, which are updated every time the user publishes a version of Vocabularies.
Do you know whether it is possible to prevent Google Cloud from caching the files located on /content/vocabularies? for example:
https://vocabularies.cessda.eu/content/vocabularies/SamplingProcedure/SamplingProcedure.json
I have tested by retrieving the JSON files from the above link (with cache disabled on Postman/Web-Browser), and as you can see from the file size, that the JSON files retrieved from Google cloud are mixed between the current version and the older cached version.
Which causing sometimes the DE version to disappear on the Samplig Procedure
The static JSON files are currently used for the publication side and the /v2 rest APIs. so they are really important not to be in cached. If it is not possible to prevent this google-cloud cache, then probably I need to move the storage of published vocabularies to the database which is major change.
Update:
Turns out that the issue is due to incorrect HTTP Headers (4 years max-age & incorrect content type). Thus, the title of the issue is updated from “Prevent the cache of the published-Vocabularies stored in the static JSON files“ to “Fix incorrect HTTP headers related to cache-control and content-type for JSON files“