Closed anders-kiaer closed 2 years ago
After some detailed debugging, turned out this is not related to ngx_brotli
at all - and was due to same as described here https://stackoverflow.com/q/66385965 and the cloud vendor persisting volumes across deploys even when they say volumes will not persist.
Sorry for the noise. :slightly_smiling_face:
With the following example
nginx.conf
snippet:we correctly get the
[...].js.br
versions when requesting[...].js
onlocalhost
, but when deployed to cloud service web app the uncompressed file[...].js
is returned despite both scenarios haveAccept encoding: gzip, deflate, br
sent by the Chrome browser.If adding
as well, we still correctly get the statically compressed files on
localhost
, and in deployed app we get dynamically compressed versions (i.e. they are compressed, but not the expected statically compressed files).I.e. the problem appears to be limited to statically compressed file not on localhost.
Any input on how to debug or what this could be due to? E.g. is
localhost
and external server treated differently and requires differentnginx
setups, or could it be related tohttp
(localhost
) andhttps
when accessing it on the cloud app? Or related to cloud vendor probably having their own proxy in front of ours? Forgzip
there isgzip_proxied
, but this appears not to be necessary to configure withngx_brotli
according to #53. :thinking: