DevFW-CICD/ingress-nginx-helm
16
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fix typo about the kind of request

Browse source
This commit is contained in:
Eugene Pirogov 2018-05-16 09:53:17 +03:00 committed by GitHub
parent 7dc256a9f9
commit 3ffbe5f9c5
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/user-guide/nginx-configuration/annotations.md
View file

@ -329,7 +329,7 @@ Additionally it is possible to set:
* `nginx.ingress.kubernetes.io/auth-signin`: * `nginx.ingress.kubernetes.io/auth-signin`:
`<SignIn_URL>` to specify the location of the error page. `<SignIn_URL>` to specify the location of the error page.
* `nginx.ingress.kubernetes.io/auth-response-headers`: * `nginx.ingress.kubernetes.io/auth-response-headers`:
`<Response_Header_1, ..., Response_Header_n>` to specify headers to pass to backend once authorization request completes. `<Response_Header_1, ..., Response_Header_n>` to specify headers to pass to backend once authentication request completes.
* `nginx.ingress.kubernetes.io/auth-request-redirect`: * `nginx.ingress.kubernetes.io/auth-request-redirect`:
`<Request_Redirect_URL>` to specify the X-Auth-Request-Redirect header value. `<Request_Redirect_URL>` to specify the X-Auth-Request-Redirect header value.
@ -553,4 +553,4 @@ Additionally, if the gRPC service requires TLS, add `nginx.ingress.kubernetes.io
This feature requires HTTP2 to work which means we need to expose this service using HTTPS. This feature requires HTTP2 to work which means we need to expose this service using HTTPS.
Exposing a gRPC service using HTTP is not supported. Exposing a gRPC service using HTTP is not supported.
[configmap]: ./configmap.md [configmap]: ./configmap.md