About caching
Right now there are now caching headers upstream with SearXNG. This fork adds a no-cache header to every request to make sure that users always load the most recent static files like js and css. The site would look broken in the past when there was a 12h public cache policy where the client would not load or even check for a newer file version.
The caching should be handled upstream either with etags (so its like a checksum and the file gets fetched from upstream if it does not match with local cache) or by using versioning for the files. Meaning: Add like a 1year public cache to the static file and rename the static file very time it changes (so searxng.1.1.1.min.css and after a change searxng.1.1.2.css and so on) this way we have a fast cache and files get always fetched from upstream in case of a change...