doc: fix --inspect security warning section#61675
Merged
nodejs-github-bot merged 1 commit intonodejs:mainfrom Feb 6, 2026
Merged
doc: fix --inspect security warning section#61675nodejs-github-bot merged 1 commit intonodejs:mainfrom
nodejs-github-bot merged 1 commit intonodejs:mainfrom
Conversation
nodejs-github-bot
added
cli
cjihrig
approved these changes
Feb 4, 2026
legendecas
approved these changes
Feb 4, 2026
bnb
approved these changes
Feb 4, 2026
UlisesGascon
approved these changes
Feb 5, 2026
legendecas
added
author ready
nodejs-github-bot
removed
the
commit-queue
Collaborator
|
Landed in 9bc369f |
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
6 participants
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.
In the current docs, somehow this has ended up nested within the
--insecure-http-parsersection above the various inspect options. It ends up in the wrong place in the ToC, and isn't visible at all if you jump to the inspect sections, which rather defeats the point.I've moved it into the
--inspectoption itself, and updated the text of each related option above to more clearly link to the warning there below.