Browsers are caching a stale config.js
Problem/Opportunity Statement
Message from a JS2 community member:
I believe that !928 (merged) (merged 2 days ago) triggered this issue, but is not the underlying cause.
What would success / a fix look like?
Maybe we set a Cache-Control
header to no-cache
or must-revalidate
. For config.js
alone or most/all static files that we serve? This needs a bit of design work.