NGX-738: Add caching for 301 redirects in NGINX configuration #32
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
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.
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 commit introduces caching for 301 redirect responses in the NGINX configuration. The 'proxy_cache_valid' directive has been updated to cache 301 status codes for a default period specified by the 'nginx_cache_time_default' variable. This change aims to improve performance by reducing the load on the server for frequently accessed redirected URLs and ensures a faster response time for end users. The caching durations for 200 and 404 status codes remain unchanged.
Related to performance optimization efforts.