docs: document IP_CUSTOM_HEADER_WARNINGS env var#769
Closed
dstockton wants to merge 1 commit into
Closed
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Closed
11 tasks
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
1 participant
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.
Documents the new
IP_CUSTOM_HEADER_WARNINGSenvironment variable added in directus/directus.When
IP_CUSTOM_HEADERis set, Directus logs a warning on every request where that header is absent or not a valid IP. Behind a proxy that also health-checks the origin directly (or receives non-proxied traffic), this fires constantly. The new variable (defaulttrue) lets operators set it tofalseto silence the warning.Code PR: directus/directus#27901
Linear: CMS-2827