This helps avoid caches incorrectly returning "304 Not Changed". Some brief testing seems to indicate that query strings does correctly cause a cache hit on our webserver (Cloudflare?)
We can also consider moving the hosting (haha) to something like Cloudflare Pages which allows us to control HTTP headers.
This solution isn't optimal, we should be using a Jekyll hook to change the filename and the defined path in the HTML, since caching on query strings is not clearly defined across caching proxies.
This helps avoid caches incorrectly returning "304 Not Changed". Some brief testing seems to indicate that query strings does correctly cause a cache hit on our webserver (Cloudflare?)
We can also consider moving the hosting (haha) to something like Cloudflare Pages which allows us to control HTTP headers.
This solution isn't optimal, we should be using a Jekyll hook to change the filename and the defined path in the HTML, since caching on query strings is not clearly defined across caching proxies.