NGF: Update upstream settings policy guide #1627
Merged
salonichf5 merged 1 commit intonginx:ngf-release-2.4from Jan 6, 2026
Merged
NGF: Update upstream settings policy guide #1627salonichf5 merged 1 commit intonginx:ngf-release-2.4from
salonichf5 merged 1 commit intonginx:ngf-release-2.4from
Conversation
sjberman
approved these changes
Jan 5, 2026
bjee19
approved these changes
Jan 5, 2026
bjee19
pushed a commit
that referenced
this pull request
Jan 27, 2026
Update upstream settings policy guide for keepAlive
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.
Proposed changes
Updates the upstream settings policy guide to showcase information about updating or disabling
keepAlivedirective.Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩