From 4bf7f888d038dfe77d071be3195c86756982a154 Mon Sep 17 00:00:00 2001 From: Steve Kamerman Date: Fri, 20 Nov 2015 17:47:08 -0500 Subject: [PATCH] Documented HTTPS_METHOD --- README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 9d4bb40..2b8dcf8 100644 --- a/README.md +++ b/README.md @@ -110,7 +110,7 @@ should provide compatibility with clients back to Firefox 1, Chrome 1, IE 7, Ope Windows XP IE8, Android 2.3, Java 7. The configuration also enables HSTS, and SSL session caches. -The behavior for the proxy when port 80 and 443 are exposed is as follows: +The default behavior for the proxy when port 80 and 443 are exposed is as follows: * If a container has a usable cert, port 80 will redirect to 443 for that container so that HTTPS is always preferred when available. @@ -121,6 +121,10 @@ to establish a connection. A self-signed or generic cert named `default.crt` an will allow a client browser to make a SSL connection (likely w/ a warning) and subsequently receive a 503. +To serve traffic in both SSL and non-SSL modes without redirecting to SSL, you can include the +environment variable `HTTPS_METHOD=noredirect` (the default is `HTTPS_METHOD=redirect`). You can also +disable the non-SSL site entirely with `HTTPS_METHOD=nohttp` + ### Basic Authentication Support In order to be able to secure your virtual host, you have to create a file named as its equivalent VIRTUAL_HOST variable on directory