-
Notifications
You must be signed in to change notification settings - Fork 25.6k
[DOCS] Clarify HTTP and transport TLS settings #79952
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
lockewritesdocs
merged 2 commits into
elastic:master
from
lockewritesdocs:docs__clarify-ssl-settings
Oct 27, 2021
Merged
[DOCS] Clarify HTTP and transport TLS settings #79952
lockewritesdocs
merged 2 commits into
elastic:master
from
lockewritesdocs:docs__clarify-ssl-settings
Oct 27, 2021
+3
−1
Conversation
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
Collaborator
|
Pinging @elastic/es-docs (Team:Docs) |
Collaborator
|
Pinging @elastic/es-security (Team:Security) |
Contributor
Author
|
@elasticmachine update branch |
lcawl
approved these changes
Oct 27, 2021
Contributor
lcawl
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
lockewritesdocs
pushed a commit
to lockewritesdocs/elasticsearch
that referenced
this pull request
Oct 27, 2021
Co-authored-by: Elastic Machine <[email protected]>
lockewritesdocs
pushed a commit
to lockewritesdocs/elasticsearch
that referenced
this pull request
Oct 27, 2021
Co-authored-by: Elastic Machine <[email protected]>
lockewritesdocs
pushed a commit
to lockewritesdocs/elasticsearch
that referenced
this pull request
Oct 27, 2021
Co-authored-by: Elastic Machine <[email protected]>
Collaborator
elasticsearchmachine
pushed a commit
that referenced
this pull request
Oct 27, 2021
Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Elastic Machine <[email protected]>
elasticsearchmachine
pushed a commit
that referenced
this pull request
Oct 27, 2021
Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Elastic Machine <[email protected]>
elasticsearchmachine
pushed a commit
that referenced
this pull request
Oct 27, 2021
Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Elastic Machine <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
>docs
General docs changes
:Security/Security
Security issues without another label
Team:Docs
Meta label for docs team
Team:Security
Meta label for security team
v7.15.1
v7.16.0
v8.0.0-beta1
v8.1.0
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.
A user on the Discuss forums indicated their confusion between
xpack.security.http.ssl.enabledandxpack.security.transport.ssl.enabled. This PR clarifies each of these settings to distinguish them from one another.