Update http.markdown to clarify ip_ban_enabled required parameters #41776
+1
−1
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.
The login_attempts_threshold parameter is required if ip_ban_enabled is set to true. The default of "-1" for the login_attempts_threshold effectively turns it off. I've updated the sentence about these parameters to make it clearer that both must be set in order to use the functionality.
Proposed change
This is a documentation update which clarifies that an optional parameter (login_attempts_threshold) is required if another optional parameter (ip_ban_enabled) is set to true in the http integration.
Type of change
This clarifies that the login_attempts_threshold is required to be set if ip_ban_enabled is set to true.
currentbranch).currentbranch).nextbranch).nextbranch).Additional information
Checklist
currentbranch.nextbranch.