Skip to content
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

Document some configuration for HTTPS #799

Merged
merged 1 commit into from
Mar 18, 2015
Merged

Document some configuration for HTTPS #799

merged 1 commit into from
Mar 18, 2015

Conversation

tummychow
Copy link
Contributor

A few configuration changes introduced by the HTTPS API feature in 0.5.0 that hadn't been written down.

- the HTTPS API address can be configured just like any other address
- the verify_incoming setting also applies to the HTTPS API
@@ -546,7 +547,7 @@ definitions support being updated during a reload.
connections make use of TLS and that the client provides a certificate signed
by the Certificate Authority from the [`ca_file`](#ca_file). By default, this is false, and
Consul will not enforce the use of TLS or verify a client's authenticity. This
only applies to Consul servers since a client never has an incoming connection.
applies to both server RPC and to the HTTPS API.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this should still clearly indicate that it only affects server nodes. Consider

This only applies to Consul servers, since a client never has an incoming connection. It affects both the RPC and HTTPS interfaces.

@ryanuber
Copy link
Member

LGTM, other than the minor suggestion above. Thanks!

@ryanuber
Copy link
Member

I think I replied too quickly on this one, sorry about that. Makes sense after a second read. Thanks!

ryanuber added a commit that referenced this pull request Mar 18, 2015
Document some configuration for HTTPS
@ryanuber ryanuber merged commit d445f64 into hashicorp:master Mar 18, 2015
@tummychow tummychow deleted the https-docs branch March 18, 2015 23:27
duckhan pushed a commit to duckhan/consul that referenced this pull request Oct 24, 2021
* Don't run them in parallel so that we only get one slack notification
* Add gotestsum summary
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants