Alan Orth aabb783d99
app.yaml: Set Cache-Control header to private for CSS
Google App Engine agressively caches stuff. They are currently serving
a 24-hour old version of my CSS after multiple updates and re-deploys.
Ughhh. From their docs:

> After a file is transmitted with a given expiration time, there is
> generally no way to clear it out of web-proxy caches, even if the user
> clears their own browser cache. Re-deploying a new version of the app
> will not reset any caches. Therefore, if you ever plan to modify a
> static file, it should have a short (less than one hour) expiration
> time. In most cases, the default 10-minute expiration time is
> appropriate.

The only way to break this for now is to change the CSS *directory*.
In the future I think we have to be sure to set the private cache
control header, which lets browsers cache it, but not public CDNs.

See: https://cloud.google.com/appengine/docs/standard/python3/how-requests-are-handled
2021-03-14 11:58:57 +02:00
2021-03-14 11:41:48 +02:00
2021-03-14 11:42:07 +02:00
2021-03-14 11:41:48 +02:00
2021-03-11 20:26:33 +02:00
2021-03-14 10:08:44 +02:00
2021-03-14 10:09:18 +02:00
2021-03-14 10:09:18 +02:00
2021-03-12 22:59:57 +02:00
Description
Easy to use, web-based version of the DSpace CSV Metadata Quality checker application.
https://fierce-ocean-30836.herokuapp.com 818 KiB
Languages
HTML 53%
Python 39.1%
SCSS 7.9%