diff options
author | Ryan Lahfa <masterancpp@gmail.com> | 2024-01-14 04:55:27 +0100 |
---|---|---|
committer | GitHub <noreply@github.com> | 2024-01-14 04:55:27 +0100 |
commit | dd5621df6dcb90122b50da5ec31c411a0de3e538 (patch) | |
tree | 304acbcd0eb544a717dd4d4b9fa48a1634e239dd /doc | |
parent | a05a3c08f1a61489496d4da10ef5f13580491c72 (diff) | |
parent | f124c7368678ce28618d92f3d071a379c936c72a (diff) | |
download | nixlib-dd5621df6dcb90122b50da5ec31c411a0de3e538.tar nixlib-dd5621df6dcb90122b50da5ec31c411a0de3e538.tar.gz nixlib-dd5621df6dcb90122b50da5ec31c411a0de3e538.tar.bz2 nixlib-dd5621df6dcb90122b50da5ec31c411a0de3e538.tar.lz nixlib-dd5621df6dcb90122b50da5ec31c411a0de3e538.tar.xz nixlib-dd5621df6dcb90122b50da5ec31c411a0de3e538.tar.zst nixlib-dd5621df6dcb90122b50da5ec31c411a0de3e538.zip |
Merge pull request #278380 from DeeUnderscore/fix/nginx-etag
nginx: change etags for statically compressed files served from store
Diffstat (limited to 'doc')
-rw-r--r-- | doc/packages/nginx.section.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/packages/nginx.section.md b/doc/packages/nginx.section.md index 0704b534e5f7..41241304ceff 100644 --- a/doc/packages/nginx.section.md +++ b/doc/packages/nginx.section.md @@ -8,4 +8,4 @@ HTTP has a couple of different mechanisms for caching to prevent clients from ha Fortunately, HTTP supports an alternative (and more effective) caching mechanism: the [`ETag`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/ETag) response header. The value of the `ETag` header specifies some identifier for the particular content that the server is sending (e.g., a hash). When a client makes a second request for the same resource, it sends that value back in an `If-None-Match` header. If the ETag value is unchanged, then the server does not need to resend the content. -As of NixOS 19.09, the nginx package in Nixpkgs is patched such that when nginx serves a file out of `/nix/store`, the hash in the store path is used as the `ETag` header in the HTTP response, thus providing proper caching functionality. This happens automatically; you do not need to do modify any configuration to get this behavior. +As of NixOS 19.09, the nginx package in Nixpkgs is patched such that when nginx serves a file out of `/nix/store`, the hash in the store path is used as the `ETag` header in the HTTP response, thus providing proper caching functionality. With NixOS 24.05 and later, the `ETag` additionally includes the response content length, to ensure files served with static compression do not share `ETag`s with their uncompressed version. This `ETag` functionality is enabled automatically; you do not need to do modify any configuration to get this behavior. |