Skip to content
This repository has been archived by the owner on May 7, 2020. It is now read-only.

Content passing through auth-proxy should remain gzipped #235

Open
wpears opened this issue May 24, 2018 · 3 comments
Open

Content passing through auth-proxy should remain gzipped #235

wpears opened this issue May 24, 2018 · 3 comments
Assignees

Comments

@wpears
Copy link
Member

wpears commented May 24, 2018

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).

@wpears
Copy link
Member Author

wpears commented May 24, 2018

@hkeeler

@wpears wpears self-assigned this May 24, 2018
@wpears
Copy link
Member Author

wpears commented May 24, 2018

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.

@wpears
Copy link
Member Author

wpears commented May 24, 2018

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant