You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-[Default TLS Version and Ciphers](#default-tls-version-and-ciphers)
10
+
-[Legacy TLS](#legacy-tls)
9
11
10
12
## Default SSL Certificate
11
13
@@ -130,7 +132,7 @@ By default the controller redirects (301) to HTTPS if there is a TLS Ingress rul
130
132
131
133
To disable this behavior use `hsts: "false"` in the configuration ConfigMap.
132
134
133
-
###Server-side HTTPS enforcement through redirect
135
+
## Server-side HTTPS enforcement through redirect
134
136
135
137
By default the controller redirects (301) to `HTTPS` if TLS is enabled for that ingress. If you want to disable that behavior globally, you can use `ssl-redirect: "false"` in the NGINX config map.
136
138
@@ -152,3 +154,22 @@ version to fully support Kube-Lego is nginx Ingress controller 0.8.
To provide the most secure baseline configuration possible, nginx-ingress defaults to using TLS 1.2 and a [secure set of TLS ciphers](https://github.com/kubernetes/ingress-nginx/blob/master/docs/user-guide/configmap.md#ssl-ciphers)
161
+
162
+
## Legacy TLS
163
+
The default configuration, though secure, does not support some older browsers and operating systems. For instance, 20% of Android phones in use today are not compatible with nginx-ingress's default configuration. To change this default behavior, use a [ConfigMap](https://github.com/kubernetes/ingress-nginx/blob/master/docs/user-guide/configmap.md#ssl-ciphers).
164
+
165
+
A sample ConfigMap to allow these older clients connect could look something like the following:
0 commit comments