Automatic certs loading

All certificates located in the /certs directory are now loaded automatically. This feature makes the CERTS environment variable deprecated.

serviceDomainMatchAll reconfigure parameter

Added serviceDomainMatchAll reconfigure parameter that allows to include subdomains and FDQN domains in the match.

Please see the serviceDomainMatchAll parameter in the reconfigure section of the documentation.

fromListener and recreate params for the reload request

Added the feature to recreate the config during the reload request. Config can be recreated through recreate and fromListenerparams. The first param recreates config from memory while the second fetches data from Docker Flow Swarm Listener. Please consult Reload section of the documentation for more info.

Secrets suport

Support for Docker secrets has been added. Any environment variable can be overwritten by a secret.

Please read the Secrets section of the documentation for more info.

Proxy Statistics section contains an example.

EXTRA_GLOBAL environment variable

Added support for extra text for the global config section. Please take a look at the EXTRA_GLOBAL variable in the Configuring Docker Flow Proxy documentation.

timeoutServer and timeoutTunnel reconfigure parameters

Added timeoutServer and timeoutTunnel reconfigure parameters. For more info, please consult the Usage documentation.

TIMEOUT_TUNNEL env. variable

Added environment variable TIMEOUT_TUNNEL that provide the ability to change the default value of the timeout tunnel configuration. Please see the configuration page for more info.

httpsOnly

A new reconfigure parameter httpsOnly was added. If set to true, HTTP requests to the service will be redirected to HTTPS.

TCP Requests Support

Added reqMode parameter that allows tcp configurations.

Please read the Reconfigure section for the parameters usage and the Using TCP Request Mode section of the Docker Flow: Proxy - Swarm Mode (Docker 1.12+) With Automatic Configuration article for an example.

Multiple destinations & templates documentation

Multiple Destinations

Multiple destinations for a single service can be specified by adding index as a suffix to servicePath and port parameters. In that case, srcPort is required. Defining multiple destinations is useful in cases when a service exposes multiple ports with different paths and functions.

An example request is as follows.

<PROXY_IP>:<PROXY_PORT>/v1/docker-flow-proxy/reconfigure?serviceName=foo&servicePath.1=/&port.1=8080&srcPort.1=80&servicePath.2=/&port.2=8081&srcPort.2=443

The command would create a service foo that exposes ports 8080 and 8081. All requests coming to proxy port 80 with the path that starts with / will be forwarded to the service foo port 8080. Equally, all requests coming to proxy port 443 (HTTPS) with the path that starts with / will be forwarded to the service foo port 8081.

Indexes are incremental and start with 1.

Templates Documentation

Added documentation about the usage of front-end and back-end templates.