HTTP Client

HTTP Proxy

If the application needs to use an HTTP proxy to access external resources, it can be configured as follows.

In this example, the HTTP proxy URL is http://localhost:8888. Connections to hosts listed under nonProxyHosts are made directly and not through the HTTP proxy. In this example, this would be localhost, any IP address starting with 192.168. and any subdomain of example.org.

httpClient:
 proxy:
   host: localhost
   port: 8888
   scheme : http
   nonProxyHosts:
     - localhost
     - '192.168.*'
     - '*.example.org'

TLS

When the application connects to an external service over https (for example a WFS or tile backend), the following settings control how the certificate of the remote service is validated. The current defaults are verifyHostname: false and trustSelfSignedCertificates: true, i.e. the hostname of the certificate is not verified and self-signed certificates are accepted. For connections to services with valid certificates it is recommended to enable strict validation:

httpClient:
 tls:
   verifyHostname: true
   trustSelfSignedCertificates: false

In v5.0 these secure values will become the defaults. Deployments that connect to services with self-signed or otherwise non-verifiable certificates will then have to set verifyHostname: false and trustSelfSignedCertificates: true explicitly.