Some, additional thoughts:
We have two separate files:
select2.full.min.js.gz
select2.full.min.js
A discussion from from 2015 suggests that Nginx computes ETags using last
modified time and content length.
SOURCE:
https://serverfault.com/questions/690341/algorithm-behind-nginx-etag-generation
It is possible to configure Nginx with: gzip_static always;
This will always retrieve data from the gzip'ed file and then use the
ngx_http_gunzip_module module to decompress the data before sending it to
clients that do not support "Content-Encoding: gzip"; additional checks may
be warranted to verify that the ETag truly only depends on the file timestamp.
On 6/25/24 10:03 AM, Simon Déziel wrote:
> @pinnion, I'm still seeing differing ETags between those 2:
>
> $ wget -qSO /dev/null
> https://staging.dashboard.villadeus.com/js/select2.full.min.js.gz 2>&1 | grep
> ETag
> ETag: "667af11b-520f"
> $ wget --compress gzip -qSO /dev/null
> https://staging.dashboard.villadeus.com/js/select2.full.min.js 2>&1 | grep
> ETag
> ETag: "667af11b-124fd"
>
>
> Also, re `touch *`, I'm not entirely sure on how you are doing the "ahead of
> time compression" but I get good result from `gzip --best --keep --force
> --no-name` which cause the `.gz` files to be created with a newer timestamp
> naturally.
>
--
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
