Cache-Control: immutable

Adding "immutable" means that the browser should not even check the ETag if those files are cached. That saves a network connection and response round trip. That should reduce the load on the webserver some, but only really number of active TCP connections, rather than bandwidth, since the files were already being cached. This probably will only reduce the peak load a little bit since this doesn't affect index and APK downloads, but it will make page loads more responsive during peak load times.

• https://hacks.mozilla.org/2017/01/using-immutable-caching-to-speed-up-the-web/
• https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control
• https://www.keycdn.com/blog/cache-control-immutable

Based on this thread with @Joost: https://forum.f-droid.org/t/slow-webserver-response/6968/15

@uniqx @redplanet @IzzySoft or anyone else who knows webby things: are there any risks of enabling this that we should be aware of?