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

Fix doc links (#1925)

Browse source 
* Fix documentation links
* Replace external-traffic annotation
* Update awesome_bot docker image
This commit is contained in:
Manuel Alejandro de Brito Fontes 2018-01-18 13:30:29 -02:00 • committed by GitHub
parent b50cdc0256
commit 5a16a7aaa0
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
9 changed files with 11 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/user-guide/custom-errors.md
View file

@ -8,7 +8,7 @@ Each request to the default backend includes two headers:
**Important:** the custom backend must return the correct HTTP status code to be returned. NGINX do not changes the response from the custom default backend.
Using this two headers is possible to use a custom backend service like [this one](https://github.com/kubernetes/ingress-nginx/tree/master/examples/customization/custom-errors/nginx) that inspect each request and returns a custom error page with the format expected by the client. Please check the example [custom-errors](examples/customization/custom-errors/README.md)
Using this two headers is possible to use a custom backend service like [this one](https://github.com/kubernetes/ingress-nginx/tree/master/images/custom-error-pages) that inspect each request and returns a custom error page with the format expected by the client. Please check the example [custom-errors](https://github.com/kubernetes/ingress-nginx/tree/master/docs/examples/customization/custom-errors)
NGINX sends additional headers that can be used to build custom response: