This repository has been archived on 2020-08-01. You can view files and clone it, but cannot push or open issues or pull requests.
nginx-proxy/nginx.tmpl

181 lines
6.6 KiB
Cheetah
Raw Normal View History

{{ define "upstream" }}
{{ if .Address }}
{{/* If we got the containers from swarm and this container's port is published to host, use host IP:PORT */}}
{{ if and .Container.Node.ID .Address.HostPort }}
# {{ .Container.Node.Name }}/{{ .Container.Name }}
server {{ .Container.Node.Address.IP }}:{{ .Address.HostPort }};
{{/* If there is no swarm node or the port is not published on host, use container's IP:PORT */}}
{{ else }}
# {{ .Container.Name }}
server {{ .Address.IP }}:{{ .Address.Port }};
{{ end }}
{{ else }}
# {{ .Container.Name }}
server {{ .Container.IP }} down;
{{ end }}
{{ end }}
# If we receive X-Forwarded-Proto, pass it through; otherwise, pass along the
# scheme used to connect to this server
map $http_x_forwarded_proto $proxy_x_forwarded_proto {
default $http_x_forwarded_proto;
'' $scheme;
}
# If we receive Upgrade, set Connection to "upgrade"; otherwise, delete any
# Connection header that may have been passed to this server
map $http_upgrade $proxy_connection {
default upgrade;
2015-05-09 23:15:26 +02:00
'' close;
}
gzip_types text/plain text/css application/javascript application/json application/x-javascript text/xml application/xml application/xml+rss text/javascript;
2014-12-07 02:46:25 +01:00
log_format vhost '$host $remote_addr - $remote_user [$time_local] '
'"$request" $status $body_bytes_sent '
'"$http_referer" "$http_user_agent"';
access_log off;
# HTTP 1.1 support
proxy_http_version 1.1;
proxy_buffering off;
proxy_set_header Host $http_host;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $proxy_connection;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $proxy_x_forwarded_proto;
server {
server_name _; # This is just an invalid value which will never trigger on a real hostname.
2015-07-24 10:39:56 +02:00
listen 80;
access_log /var/log/nginx/access.log vhost;
return 503;
}
{{ if (and (exists "/etc/nginx/certs/default.crt") (exists "/etc/nginx/certs/default.key")) }}
server {
server_name _; # This is just an invalid value which will never trigger on a real hostname.
listen 443 ssl spdy;
return 503;
ssl_certificate /etc/nginx/certs/default.crt;
ssl_certificate_key /etc/nginx/certs/default.key;
}
{{ end }}
{{ range $host, $containers := groupByMulti $ "Env.VIRTUAL_HOST" "," }}
Add SSL support This adds SSL support for containers. It supports single host certificates, wildcards and SNI using naming conventions for certificates or optionally specify a cert name (for SNI). The SSL cipher configuration is based on mozilla intermediate profile which should provide compatibility with clients back to Firefox 1, Chrome 1, IE 7, Opera 5, Safari 1, Windows XP IE8, Android 2.3, Java 7. The configuration also enables OCSP stapling, HSTS, and ssl session caches. To enable SSL, nginx-proxy should be started w/ -p 443:443 and -v /path/to/certs:/etc/nginx/certs. Certificates must be named: <virtualhost>.crt and <virtualhost>.key where <virtualhost> matches the a value of VIRTUAL_HOST on a container. For wildcard certificates, the certificate and private key should be named after the wildcard domain with .crt and .key suffixes. For example, *.example.com should be name example.com.crt and example.com.key. For SNI where a certificate may be used for multiple domain names, the container can specify a CERT_NAME env var that corresponds to the base file name of the certificate and key. For example, if you have a cert allowing *.example.com and *.bar.com, it can be name shared.crt and shared.key. A container can use that cert by having CERT_NAME=shared and VIRTUAL_HOST=foo.example.com. The name "shared" is arbitrary and can be whatever makes sense. The behavior for the proxy when port 80 and 443 is defined is as follows: * If a container has a usable cert, port 80 will redirect to 443 for that container to always prefer HTTPS when available. * If the container does not have a usable cert 503 will be returned. In the last case, a self-signed or generic cert can be defined as "default.crt" and "default.key" which will allow a client browser to at least make a SSL connection.
2014-11-26 18:38:51 +01:00
2014-05-05 18:59:23 +02:00
upstream {{ $host }} {
{{ range $container := $containers }}
{{ $addrLen := len $container.Addresses }}
{{/* If only 1 port exposed, use that */}}
{{ if eq $addrLen 1 }}
{{ $address := index $container.Addresses 0 }}
{{ template "upstream" (dict "Container" $container "Address" $address) }}
{{/* If more than one port exposed, use the one matching VIRTUAL_PORT env var, falling back to standard web port 80 */}}
{{ else }}
{{ $port := coalesce $container.Env.VIRTUAL_PORT "80" }}
{{ $address := where $container.Addresses "Port" $port | first }}
{{ template "upstream" (dict "Container" $container "Address" $address) }}
{{ end }}
{{ end }}
2014-05-05 18:59:23 +02:00
}
2015-07-26 11:38:45 +02:00
{{ $default_host := or ($.Env.DEFAULT_HOST) "" }}
{{ $default_server := index (dict $host "" $default_host "default_server") $host }}
2015-07-24 10:39:56 +02:00
{{/* Get the VIRTUAL_PROTO defined by containers w/ the same vhost, falling back to "http" */}}
{{ $proto := or (first (groupByKeys $containers "Env.VIRTUAL_PROTO")) "http" }}
Add SSL support This adds SSL support for containers. It supports single host certificates, wildcards and SNI using naming conventions for certificates or optionally specify a cert name (for SNI). The SSL cipher configuration is based on mozilla intermediate profile which should provide compatibility with clients back to Firefox 1, Chrome 1, IE 7, Opera 5, Safari 1, Windows XP IE8, Android 2.3, Java 7. The configuration also enables OCSP stapling, HSTS, and ssl session caches. To enable SSL, nginx-proxy should be started w/ -p 443:443 and -v /path/to/certs:/etc/nginx/certs. Certificates must be named: <virtualhost>.crt and <virtualhost>.key where <virtualhost> matches the a value of VIRTUAL_HOST on a container. For wildcard certificates, the certificate and private key should be named after the wildcard domain with .crt and .key suffixes. For example, *.example.com should be name example.com.crt and example.com.key. For SNI where a certificate may be used for multiple domain names, the container can specify a CERT_NAME env var that corresponds to the base file name of the certificate and key. For example, if you have a cert allowing *.example.com and *.bar.com, it can be name shared.crt and shared.key. A container can use that cert by having CERT_NAME=shared and VIRTUAL_HOST=foo.example.com. The name "shared" is arbitrary and can be whatever makes sense. The behavior for the proxy when port 80 and 443 is defined is as follows: * If a container has a usable cert, port 80 will redirect to 443 for that container to always prefer HTTPS when available. * If the container does not have a usable cert 503 will be returned. In the last case, a self-signed or generic cert can be defined as "default.crt" and "default.key" which will allow a client browser to at least make a SSL connection.
2014-11-26 18:38:51 +01:00
{{/* Get the first cert name defined by containers w/ the same vhost */}}
{{ $certName := (first (groupByKeys $containers "Env.CERT_NAME")) }}
{{/* Get the best matching cert by name for the vhost. */}}
{{ $vhostCert := (closest (dir "/etc/nginx/certs") (printf "%s.crt" $host))}}
{{/* vhostCert is actually a filename so remove any suffixes since they are added later */}}
{{ $vhostCert := replace $vhostCert ".crt" "" -1 }}
{{ $vhostCert := replace $vhostCert ".key" "" -1 }}
{{/* Use the cert specifid on the container or fallback to the best vhost match */}}
{{ $cert := (coalesce $certName $vhostCert) }}
{{ if (and (ne $cert "") (exists (printf "/etc/nginx/certs/%s.crt" $cert)) (exists (printf "/etc/nginx/certs/%s.key" $cert))) }}
Add SSL support This adds SSL support for containers. It supports single host certificates, wildcards and SNI using naming conventions for certificates or optionally specify a cert name (for SNI). The SSL cipher configuration is based on mozilla intermediate profile which should provide compatibility with clients back to Firefox 1, Chrome 1, IE 7, Opera 5, Safari 1, Windows XP IE8, Android 2.3, Java 7. The configuration also enables OCSP stapling, HSTS, and ssl session caches. To enable SSL, nginx-proxy should be started w/ -p 443:443 and -v /path/to/certs:/etc/nginx/certs. Certificates must be named: <virtualhost>.crt and <virtualhost>.key where <virtualhost> matches the a value of VIRTUAL_HOST on a container. For wildcard certificates, the certificate and private key should be named after the wildcard domain with .crt and .key suffixes. For example, *.example.com should be name example.com.crt and example.com.key. For SNI where a certificate may be used for multiple domain names, the container can specify a CERT_NAME env var that corresponds to the base file name of the certificate and key. For example, if you have a cert allowing *.example.com and *.bar.com, it can be name shared.crt and shared.key. A container can use that cert by having CERT_NAME=shared and VIRTUAL_HOST=foo.example.com. The name "shared" is arbitrary and can be whatever makes sense. The behavior for the proxy when port 80 and 443 is defined is as follows: * If a container has a usable cert, port 80 will redirect to 443 for that container to always prefer HTTPS when available. * If the container does not have a usable cert 503 will be returned. In the last case, a self-signed or generic cert can be defined as "default.crt" and "default.key" which will allow a client browser to at least make a SSL connection.
2014-11-26 18:38:51 +01:00
server {
server_name {{ $host }};
2015-07-26 11:38:45 +02:00
listen 80 {{ $default_server }};
access_log /var/log/nginx/access.log vhost;
return 301 https://$host$request_uri;
Add SSL support This adds SSL support for containers. It supports single host certificates, wildcards and SNI using naming conventions for certificates or optionally specify a cert name (for SNI). The SSL cipher configuration is based on mozilla intermediate profile which should provide compatibility with clients back to Firefox 1, Chrome 1, IE 7, Opera 5, Safari 1, Windows XP IE8, Android 2.3, Java 7. The configuration also enables OCSP stapling, HSTS, and ssl session caches. To enable SSL, nginx-proxy should be started w/ -p 443:443 and -v /path/to/certs:/etc/nginx/certs. Certificates must be named: <virtualhost>.crt and <virtualhost>.key where <virtualhost> matches the a value of VIRTUAL_HOST on a container. For wildcard certificates, the certificate and private key should be named after the wildcard domain with .crt and .key suffixes. For example, *.example.com should be name example.com.crt and example.com.key. For SNI where a certificate may be used for multiple domain names, the container can specify a CERT_NAME env var that corresponds to the base file name of the certificate and key. For example, if you have a cert allowing *.example.com and *.bar.com, it can be name shared.crt and shared.key. A container can use that cert by having CERT_NAME=shared and VIRTUAL_HOST=foo.example.com. The name "shared" is arbitrary and can be whatever makes sense. The behavior for the proxy when port 80 and 443 is defined is as follows: * If a container has a usable cert, port 80 will redirect to 443 for that container to always prefer HTTPS when available. * If the container does not have a usable cert 503 will be returned. In the last case, a self-signed or generic cert can be defined as "default.crt" and "default.key" which will allow a client browser to at least make a SSL connection.
2014-11-26 18:38:51 +01:00
}
2014-05-05 18:59:23 +02:00
server {
server_name {{ $host }};
2015-07-26 11:38:45 +02:00
listen 443 ssl spdy {{ $default_server }};
access_log /var/log/nginx/access.log vhost;
Add SSL support This adds SSL support for containers. It supports single host certificates, wildcards and SNI using naming conventions for certificates or optionally specify a cert name (for SNI). The SSL cipher configuration is based on mozilla intermediate profile which should provide compatibility with clients back to Firefox 1, Chrome 1, IE 7, Opera 5, Safari 1, Windows XP IE8, Android 2.3, Java 7. The configuration also enables OCSP stapling, HSTS, and ssl session caches. To enable SSL, nginx-proxy should be started w/ -p 443:443 and -v /path/to/certs:/etc/nginx/certs. Certificates must be named: <virtualhost>.crt and <virtualhost>.key where <virtualhost> matches the a value of VIRTUAL_HOST on a container. For wildcard certificates, the certificate and private key should be named after the wildcard domain with .crt and .key suffixes. For example, *.example.com should be name example.com.crt and example.com.key. For SNI where a certificate may be used for multiple domain names, the container can specify a CERT_NAME env var that corresponds to the base file name of the certificate and key. For example, if you have a cert allowing *.example.com and *.bar.com, it can be name shared.crt and shared.key. A container can use that cert by having CERT_NAME=shared and VIRTUAL_HOST=foo.example.com. The name "shared" is arbitrary and can be whatever makes sense. The behavior for the proxy when port 80 and 443 is defined is as follows: * If a container has a usable cert, port 80 will redirect to 443 for that container to always prefer HTTPS when available. * If the container does not have a usable cert 503 will be returned. In the last case, a self-signed or generic cert can be defined as "default.crt" and "default.key" which will allow a client browser to at least make a SSL connection.
2014-11-26 18:38:51 +01:00
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_ciphers ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA;
ssl_prefer_server_ciphers on;
ssl_session_timeout 5m;
ssl_session_cache shared:SSL:50m;
ssl_certificate /etc/nginx/certs/{{ (printf "%s.crt" $cert) }};
ssl_certificate_key /etc/nginx/certs/{{ (printf "%s.key" $cert) }};
2015-05-21 17:43:09 +02:00
{{ if (exists (printf "/etc/nginx/certs/%s.dhparam.pem" $cert)) }}
ssl_dhparam {{ printf "/etc/nginx/certs/%s.dhparam.pem" $cert }};
{{ end }}
add_header Strict-Transport-Security "max-age=31536000";
2014-05-05 18:59:23 +02:00
{{ if (exists (printf "/etc/nginx/vhost.d/%s" $host)) }}
include {{ printf "/etc/nginx/vhost.d/%s" $host }};
{{ end }}
2014-05-05 18:59:23 +02:00
location / {
proxy_pass {{ $proto }}://{{ $host }};
2014-12-16 20:19:49 +01:00
{{ if (exists (printf "/etc/nginx/htpasswd/%s" $host)) }}
auth_basic "Restricted {{ $host }}";
auth_basic_user_file {{ (printf "/etc/nginx/htpasswd/%s" $host) }};
{{ end }}
2014-05-05 18:59:23 +02:00
}
}
Add SSL support This adds SSL support for containers. It supports single host certificates, wildcards and SNI using naming conventions for certificates or optionally specify a cert name (for SNI). The SSL cipher configuration is based on mozilla intermediate profile which should provide compatibility with clients back to Firefox 1, Chrome 1, IE 7, Opera 5, Safari 1, Windows XP IE8, Android 2.3, Java 7. The configuration also enables OCSP stapling, HSTS, and ssl session caches. To enable SSL, nginx-proxy should be started w/ -p 443:443 and -v /path/to/certs:/etc/nginx/certs. Certificates must be named: <virtualhost>.crt and <virtualhost>.key where <virtualhost> matches the a value of VIRTUAL_HOST on a container. For wildcard certificates, the certificate and private key should be named after the wildcard domain with .crt and .key suffixes. For example, *.example.com should be name example.com.crt and example.com.key. For SNI where a certificate may be used for multiple domain names, the container can specify a CERT_NAME env var that corresponds to the base file name of the certificate and key. For example, if you have a cert allowing *.example.com and *.bar.com, it can be name shared.crt and shared.key. A container can use that cert by having CERT_NAME=shared and VIRTUAL_HOST=foo.example.com. The name "shared" is arbitrary and can be whatever makes sense. The behavior for the proxy when port 80 and 443 is defined is as follows: * If a container has a usable cert, port 80 will redirect to 443 for that container to always prefer HTTPS when available. * If the container does not have a usable cert 503 will be returned. In the last case, a self-signed or generic cert can be defined as "default.crt" and "default.key" which will allow a client browser to at least make a SSL connection.
2014-11-26 18:38:51 +01:00
{{ else }}
server {
2015-07-24 10:39:56 +02:00
server_name {{ $host }};
2015-07-26 11:38:45 +02:00
listen 80 {{ $default_server }};
access_log /var/log/nginx/access.log vhost;
Add SSL support This adds SSL support for containers. It supports single host certificates, wildcards and SNI using naming conventions for certificates or optionally specify a cert name (for SNI). The SSL cipher configuration is based on mozilla intermediate profile which should provide compatibility with clients back to Firefox 1, Chrome 1, IE 7, Opera 5, Safari 1, Windows XP IE8, Android 2.3, Java 7. The configuration also enables OCSP stapling, HSTS, and ssl session caches. To enable SSL, nginx-proxy should be started w/ -p 443:443 and -v /path/to/certs:/etc/nginx/certs. Certificates must be named: <virtualhost>.crt and <virtualhost>.key where <virtualhost> matches the a value of VIRTUAL_HOST on a container. For wildcard certificates, the certificate and private key should be named after the wildcard domain with .crt and .key suffixes. For example, *.example.com should be name example.com.crt and example.com.key. For SNI where a certificate may be used for multiple domain names, the container can specify a CERT_NAME env var that corresponds to the base file name of the certificate and key. For example, if you have a cert allowing *.example.com and *.bar.com, it can be name shared.crt and shared.key. A container can use that cert by having CERT_NAME=shared and VIRTUAL_HOST=foo.example.com. The name "shared" is arbitrary and can be whatever makes sense. The behavior for the proxy when port 80 and 443 is defined is as follows: * If a container has a usable cert, port 80 will redirect to 443 for that container to always prefer HTTPS when available. * If the container does not have a usable cert 503 will be returned. In the last case, a self-signed or generic cert can be defined as "default.crt" and "default.key" which will allow a client browser to at least make a SSL connection.
2014-11-26 18:38:51 +01:00
{{ if (exists (printf "/etc/nginx/vhost.d/%s" $host)) }}
include {{ printf "/etc/nginx/vhost.d/%s" $host }};
{{ end }}
Add SSL support This adds SSL support for containers. It supports single host certificates, wildcards and SNI using naming conventions for certificates or optionally specify a cert name (for SNI). The SSL cipher configuration is based on mozilla intermediate profile which should provide compatibility with clients back to Firefox 1, Chrome 1, IE 7, Opera 5, Safari 1, Windows XP IE8, Android 2.3, Java 7. The configuration also enables OCSP stapling, HSTS, and ssl session caches. To enable SSL, nginx-proxy should be started w/ -p 443:443 and -v /path/to/certs:/etc/nginx/certs. Certificates must be named: <virtualhost>.crt and <virtualhost>.key where <virtualhost> matches the a value of VIRTUAL_HOST on a container. For wildcard certificates, the certificate and private key should be named after the wildcard domain with .crt and .key suffixes. For example, *.example.com should be name example.com.crt and example.com.key. For SNI where a certificate may be used for multiple domain names, the container can specify a CERT_NAME env var that corresponds to the base file name of the certificate and key. For example, if you have a cert allowing *.example.com and *.bar.com, it can be name shared.crt and shared.key. A container can use that cert by having CERT_NAME=shared and VIRTUAL_HOST=foo.example.com. The name "shared" is arbitrary and can be whatever makes sense. The behavior for the proxy when port 80 and 443 is defined is as follows: * If a container has a usable cert, port 80 will redirect to 443 for that container to always prefer HTTPS when available. * If the container does not have a usable cert 503 will be returned. In the last case, a self-signed or generic cert can be defined as "default.crt" and "default.key" which will allow a client browser to at least make a SSL connection.
2014-11-26 18:38:51 +01:00
location / {
proxy_pass {{ $proto }}://{{ $host }};
2014-12-16 20:19:49 +01:00
{{ if (exists (printf "/etc/nginx/htpasswd/%s" $host)) }}
auth_basic "Restricted {{ $host }}";
auth_basic_user_file {{ (printf "/etc/nginx/htpasswd/%s" $host) }};
{{ end }}
Add SSL support This adds SSL support for containers. It supports single host certificates, wildcards and SNI using naming conventions for certificates or optionally specify a cert name (for SNI). The SSL cipher configuration is based on mozilla intermediate profile which should provide compatibility with clients back to Firefox 1, Chrome 1, IE 7, Opera 5, Safari 1, Windows XP IE8, Android 2.3, Java 7. The configuration also enables OCSP stapling, HSTS, and ssl session caches. To enable SSL, nginx-proxy should be started w/ -p 443:443 and -v /path/to/certs:/etc/nginx/certs. Certificates must be named: <virtualhost>.crt and <virtualhost>.key where <virtualhost> matches the a value of VIRTUAL_HOST on a container. For wildcard certificates, the certificate and private key should be named after the wildcard domain with .crt and .key suffixes. For example, *.example.com should be name example.com.crt and example.com.key. For SNI where a certificate may be used for multiple domain names, the container can specify a CERT_NAME env var that corresponds to the base file name of the certificate and key. For example, if you have a cert allowing *.example.com and *.bar.com, it can be name shared.crt and shared.key. A container can use that cert by having CERT_NAME=shared and VIRTUAL_HOST=foo.example.com. The name "shared" is arbitrary and can be whatever makes sense. The behavior for the proxy when port 80 and 443 is defined is as follows: * If a container has a usable cert, port 80 will redirect to 443 for that container to always prefer HTTPS when available. * If the container does not have a usable cert 503 will be returned. In the last case, a self-signed or generic cert can be defined as "default.crt" and "default.key" which will allow a client browser to at least make a SSL connection.
2014-11-26 18:38:51 +01:00
}
}
{{ if (and (exists "/etc/nginx/certs/default.crt") (exists "/etc/nginx/certs/default.key")) }}
Add SSL support This adds SSL support for containers. It supports single host certificates, wildcards and SNI using naming conventions for certificates or optionally specify a cert name (for SNI). The SSL cipher configuration is based on mozilla intermediate profile which should provide compatibility with clients back to Firefox 1, Chrome 1, IE 7, Opera 5, Safari 1, Windows XP IE8, Android 2.3, Java 7. The configuration also enables OCSP stapling, HSTS, and ssl session caches. To enable SSL, nginx-proxy should be started w/ -p 443:443 and -v /path/to/certs:/etc/nginx/certs. Certificates must be named: <virtualhost>.crt and <virtualhost>.key where <virtualhost> matches the a value of VIRTUAL_HOST on a container. For wildcard certificates, the certificate and private key should be named after the wildcard domain with .crt and .key suffixes. For example, *.example.com should be name example.com.crt and example.com.key. For SNI where a certificate may be used for multiple domain names, the container can specify a CERT_NAME env var that corresponds to the base file name of the certificate and key. For example, if you have a cert allowing *.example.com and *.bar.com, it can be name shared.crt and shared.key. A container can use that cert by having CERT_NAME=shared and VIRTUAL_HOST=foo.example.com. The name "shared" is arbitrary and can be whatever makes sense. The behavior for the proxy when port 80 and 443 is defined is as follows: * If a container has a usable cert, port 80 will redirect to 443 for that container to always prefer HTTPS when available. * If the container does not have a usable cert 503 will be returned. In the last case, a self-signed or generic cert can be defined as "default.crt" and "default.key" which will allow a client browser to at least make a SSL connection.
2014-11-26 18:38:51 +01:00
server {
server_name {{ $host }};
2015-07-26 11:38:45 +02:00
listen 443 ssl spdy {{ $default_server }};
access_log /var/log/nginx/access.log vhost;
Add SSL support This adds SSL support for containers. It supports single host certificates, wildcards and SNI using naming conventions for certificates or optionally specify a cert name (for SNI). The SSL cipher configuration is based on mozilla intermediate profile which should provide compatibility with clients back to Firefox 1, Chrome 1, IE 7, Opera 5, Safari 1, Windows XP IE8, Android 2.3, Java 7. The configuration also enables OCSP stapling, HSTS, and ssl session caches. To enable SSL, nginx-proxy should be started w/ -p 443:443 and -v /path/to/certs:/etc/nginx/certs. Certificates must be named: <virtualhost>.crt and <virtualhost>.key where <virtualhost> matches the a value of VIRTUAL_HOST on a container. For wildcard certificates, the certificate and private key should be named after the wildcard domain with .crt and .key suffixes. For example, *.example.com should be name example.com.crt and example.com.key. For SNI where a certificate may be used for multiple domain names, the container can specify a CERT_NAME env var that corresponds to the base file name of the certificate and key. For example, if you have a cert allowing *.example.com and *.bar.com, it can be name shared.crt and shared.key. A container can use that cert by having CERT_NAME=shared and VIRTUAL_HOST=foo.example.com. The name "shared" is arbitrary and can be whatever makes sense. The behavior for the proxy when port 80 and 443 is defined is as follows: * If a container has a usable cert, port 80 will redirect to 443 for that container to always prefer HTTPS when available. * If the container does not have a usable cert 503 will be returned. In the last case, a self-signed or generic cert can be defined as "default.crt" and "default.key" which will allow a client browser to at least make a SSL connection.
2014-11-26 18:38:51 +01:00
return 503;
ssl_certificate /etc/nginx/certs/default.crt;
ssl_certificate_key /etc/nginx/certs/default.key;
}
{{ end }}
Add SSL support This adds SSL support for containers. It supports single host certificates, wildcards and SNI using naming conventions for certificates or optionally specify a cert name (for SNI). The SSL cipher configuration is based on mozilla intermediate profile which should provide compatibility with clients back to Firefox 1, Chrome 1, IE 7, Opera 5, Safari 1, Windows XP IE8, Android 2.3, Java 7. The configuration also enables OCSP stapling, HSTS, and ssl session caches. To enable SSL, nginx-proxy should be started w/ -p 443:443 and -v /path/to/certs:/etc/nginx/certs. Certificates must be named: <virtualhost>.crt and <virtualhost>.key where <virtualhost> matches the a value of VIRTUAL_HOST on a container. For wildcard certificates, the certificate and private key should be named after the wildcard domain with .crt and .key suffixes. For example, *.example.com should be name example.com.crt and example.com.key. For SNI where a certificate may be used for multiple domain names, the container can specify a CERT_NAME env var that corresponds to the base file name of the certificate and key. For example, if you have a cert allowing *.example.com and *.bar.com, it can be name shared.crt and shared.key. A container can use that cert by having CERT_NAME=shared and VIRTUAL_HOST=foo.example.com. The name "shared" is arbitrary and can be whatever makes sense. The behavior for the proxy when port 80 and 443 is defined is as follows: * If a container has a usable cert, port 80 will redirect to 443 for that container to always prefer HTTPS when available. * If the container does not have a usable cert 503 will be returned. In the last case, a self-signed or generic cert can be defined as "default.crt" and "default.key" which will allow a client browser to at least make a SSL connection.
2014-11-26 18:38:51 +01:00
{{ end }}
2014-05-05 18:59:23 +02:00
{{ end }}