From 51e9007575e9ba2bbc7b5dfe57dbff20ae3fe4df Mon Sep 17 00:00:00 2001 From: Fred Thomsen Date: Thu, 2 Sep 2021 12:54:58 -0400 Subject: [PATCH] Add doc ref for preserve-trailing-slash annotation (#7561) Fixes issue #7555 --- docs/user-guide/nginx-configuration/annotations.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/user-guide/nginx-configuration/annotations.md b/docs/user-guide/nginx-configuration/annotations.md index 67bc10c58..e9fefebf1 100755 --- a/docs/user-guide/nginx-configuration/annotations.md +++ b/docs/user-guide/nginx-configuration/annotations.md @@ -64,6 +64,7 @@ You can add these Kubernetes annotations to specific Ingress objects to customiz |[nginx.ingress.kubernetes.io/permanent-redirect](#permanent-redirect)|string| |[nginx.ingress.kubernetes.io/permanent-redirect-code](#permanent-redirect-code)|number| |[nginx.ingress.kubernetes.io/temporal-redirect](#temporal-redirect)|string| +|[nginx.ingress.kubernetes.io/preserve-trailing-slash](#server-side-https-enforcement-through-redirect)|"true" or "false"| |[nginx.ingress.kubernetes.io/proxy-body-size](#custom-max-body-size)|string| |[nginx.ingress.kubernetes.io/proxy-cookie-domain](#proxy-cookie-domain)|string| |[nginx.ingress.kubernetes.io/proxy-cookie-path](#proxy-cookie-path)|string| @@ -591,6 +592,8 @@ When using SSL offloading outside of cluster (e.g. AWS ELB) it may be useful to even when there is no TLS certificate available. This can be achieved by using the `nginx.ingress.kubernetes.io/force-ssl-redirect: "true"` annotation in the particular resource. +To preserve the trailing slash in the URI with `ssl-redirect`, set `nginx.ingress.kubernetes.io/preserve-trailing-slash: "true"` annotation for that particular resource. + ### Redirect from/to www In some scenarios is required to redirect from `www.domain.com` to `domain.com` or vice versa.