perf: skip ETag generation for no-store responses#7010
Closed
jonathan-fulton wants to merge 1 commit intoexpressjs:masterfrom
Closed
perf: skip ETag generation for no-store responses#7010jonathan-fulton wants to merge 1 commit intoexpressjs:masterfrom
jonathan-fulton wants to merge 1 commit intoexpressjs:masterfrom
Conversation
When Cache-Control header contains 'no-store', skip ETag generation since clients will ignore it anyway. This avoids unnecessary hashing operations for responses that explicitly don't want caching. Fixes expressjs#2472
Member
|
Thanks for your contribution. We know you’re using AI, and that’s not really an issue, but please don’t duplicate work that already exists. duplicated of #6994 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
When
Cache-Control: no-storeis set, the client is required to ignore any ETag header. Generating ETags for these responses wastes CPU cycles on CRC/hash computation that the client will never use.Solution
Check the
Cache-Controlheader forno-storedirective before generating ETags. If present, skip the ETag generation entirely.Changes
lib/response.jsto check forno-storein Cache-Controlno-storeas a standalone directiveCache-Control: no-storeand combined directives likeprivate, no-store, max-age=0Performance
Eliminates unnecessary hash computation for responses that explicitly don't want caching.
Fixes #2472