I have done some experimentation regarding this on supersead, but the results needs to be verified and then possibly applied to the browser site.
The original state was that no Content-Encoding response header was sent at all, yet gzip compression was enabled in nginx (with default settings - which it seems does not include js files among others). It is unclear to me if gzip compression has indeed been used, and if it is indeed actively in use now on the browser site or not.
Needs investigation.
Take note that there's the containerized nginx in each sead cluster serving the website, and then the router nginx in the OS. Gzip-compression could potentially be enabled at any of these. We need to decide which one to use for it.
I have done some experimentation regarding this on supersead, but the results needs to be verified and then possibly applied to the browser site.
The original state was that no Content-Encoding response header was sent at all, yet gzip compression was enabled in nginx (with default settings - which it seems does not include js files among others). It is unclear to me if gzip compression has indeed been used, and if it is indeed actively in use now on the browser site or not.
Needs investigation.
Take note that there's the containerized nginx in each sead cluster serving the website, and then the router nginx in the OS. Gzip-compression could potentially be enabled at any of these. We need to decide which one to use for it.