You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 7, 2020. It is now read-only.
Gzip is enabled in nginx for all the front-end projects, but assets are being delivered to browsers with no content-encoding. My guess is that this related to an auth-proxy setting (though the problem could in fact lie elsewhere).
The text was updated successfully, but these errors were encountered:
Hmm. Actually my initial theory doesn't make sense as of course auth-proxy is still in effect in the local setup where the content encoding is being properly set. So either it is change introduced in deployment or a different part of the stack.
Hmm#2. In retrospect I don't think auth proxy actually touches these requests for static files at all. So..! This issue can probably be closed, but I'm going to leave it open until I'm on the right track.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Gzip is enabled in nginx for all the front-end projects, but assets are being delivered to browsers with no content-encoding. My guess is that this related to an auth-proxy setting (though the problem could in fact lie elsewhere).
The text was updated successfully, but these errors were encountered: