Added the cache-control to the list of forwareded headers #30
Conversation
This file contains 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 allows reverse proxy servers such as Nginx or a CloudFlare upstream to properly utilize caching with the appropriate cache keys
|
chatgpt ahh pr |
|
🙄 |
|
|
|
Man I've been spending too much time on my computer |
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.
By adding the cache-control header to the list of forwarded headers, it allows common reverse proxy applications, such as Nginx and CloudFlare in proxy mode to utilize this header normally and cache responses from the Bare server to reduce load. This is beneficial for large-scale proxy servers because it allows for a reduction in system load on the origin without impacting user experience, with the usage of an appropriately formatted cache key that includes the custom HTTP headers used in the bare protocol.