@pinnion, I just checked a random asset from your site (https://villadeus.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1) and the `gzip` version has a different ETag than the uncompressed one:
$ wget -qSO /dev/null https://villadeus.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 2>&1 | grep ETag ETag: "66720e58-15601" $ wget -qSO /dev/null https://villadeus.com/wp-includes/js/jquery/jquery.min.js.gz?ver=3.7.1 2>&1 | grep ETag ETag: "66720f0c-7656" $ wget --compress gzip -qSO /dev/null https://villadeus.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 2>&1 | grep ETag ETag: "66720f0c-7656" On one of my working system with `gzip_static` working, the ETag is always identical which makes sense if I understand the feature properly. Are you 100% sure your `gzip`'ed files are based on the uncompressed ones? `ls --full-time` might be handy to confirm. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069921 Title: gzip_static directive stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/2069921/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
