HTTP: added "not_modified_check" directive. #658
+75
−8
Conversation
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
This directive establishes four distinct modes for managing 304 responses, which determine how the If-None-Match and If-Modified-Since headers are evaluated. When the directive parameter is set to off, the response is always treated as modified, regardless of the headers. When set to any, a 304 response is returned if either the If-Modified-Since or If-None-Match condition is satisfied. When set to strict, a 304 response is returned only if both the If-Modified-Since and If-None-Match conditions are met. This is the default setting and reflects the traditional behavior of NGINX. When set to prefer_if_none_match, it will follow RFC 9110, Section 13.1.3. In this mode, if the If-None-Match header is present, the If-Modified-Since header is ignored.
7dbb2a1 to
977d853
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
2EC2
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.
This directive establishes four distinct modes for managing 304 responses, which determine how the
If-None-MatchandIf-Modified-Sinceheaders are evaluated.When the directive parameter is set to
off, the response is always treated as modified, regardless of the headers.When set to
any, a 304 response is returned if either theIf-Modified-SinceorIf-None-Matchcondition is satisfied.When set to
strict, a 304 response is returned only if both theIf-Modified-SinceandIf-None-Matchconditions are met. This is the default setting and reflects the traditional behavior of NGINX.When set to
prefer_if_none_match, it will follow RFC 9110, Section 13.1.3. In this mode, if theIf-None-Matchheader is present, theIf-Modified-Sinceheader is ignored.Proposed changes
Fixes #652