59a40db4f7
* Migrate Structure * Insert explicit ids for headers * Remove unnecessary asciidoc attributes * Copy default antora files * Fix indentation for all pages * Split files * Generate a default navigation * Remove includes * Fix cross references * Enable Section Summary TOC for small pages * WIP * Antora migration --------- Co-authored-by: Marcin Grzejszczak <mgrzejszczak@vmware.com>
53 lines
2.2 KiB
Plaintext
53 lines
2.2 KiB
Plaintext
[[accessing-backends-through-a-proxy]]
|
|
= Accessing Backends Through a Proxy
|
|
|
|
The configuration server can access a Git or Vault backend through an HTTP or HTTPS proxy.
|
|
This behavior is controlled for either Git or Vault by settings under `proxy.http` and `proxy.https`.
|
|
These settings are per repository, so if you are using a xref:server/environment-repository/composite-repositories.adoc[composite environment repository] you must configure proxy settings for each backend in the composite individually.
|
|
If using a network which requires separate proxy servers for HTTP and HTTPS URLs, you can configure both the HTTP and the HTTPS proxy settings for a single backend: in this case `http` access will use `http` proxy and `https` access the `https` one.
|
|
Also, you may specify one sole proxy that will be used for both protocols using the proxy definition protocol between application and proxy.
|
|
|
|
The following table describes the proxy configuration properties for both HTTP and HTTPS proxies. All of these properties must be prefixed by `proxy.http` or `proxy.https`.
|
|
|
|
.Proxy Configuration Properties
|
|
|===
|
|
|Property Name |Remarks
|
|
|
|
|*host*
|
|
|The host of the proxy.
|
|
|
|
|*port*
|
|
|The port with which to access the proxy.
|
|
|
|
|*nonProxyHosts*
|
|
|Any hosts which the configuration server should access outside the proxy. If values are provided for both `proxy.http.nonProxyHosts` and `proxy.https.nonProxyHosts`, the `proxy.http` value will be used.
|
|
|
|
|*username*
|
|
|The username with which to authenticate to the proxy. If values are provided for both `proxy.http.username` and `proxy.https.username`, the `proxy.http` value will be used.
|
|
|
|
|*password*
|
|
|The password with which to authenticate to the proxy. If values are provided for both `proxy.http.password` and `proxy.https.password`, the `proxy.http` value will be used.
|
|
|===
|
|
|
|
The following configuration uses an HTTPS proxy to access a Git repository.
|
|
|
|
[source,yaml]
|
|
----
|
|
spring:
|
|
profiles:
|
|
active: git
|
|
cloud:
|
|
config:
|
|
server:
|
|
git:
|
|
uri: https://github.com/spring-cloud-samples/config-repo
|
|
proxy:
|
|
https:
|
|
host: my-proxy.host.io
|
|
password: myproxypassword
|
|
port: '3128'
|
|
username: myproxyusername
|
|
nonProxyHosts: example.com
|
|
----
|
|
|