-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
431 request header fields too large annotation ignored #4593
Comments
None of those settings are related to the error you receive, but the body of the request.
The problem is in the size of the header Please adjust:
That said, from the log:
This means your application behind the service |
I added follow to the configmap Some other things
So I really think it something todo with the ingress controller. |
I deployed another ingress controller (from nginx inc) to check if I had the same issues. With nginxinc ingress controller my test works.
The headers of the nginxinc ingress contoller The headers of kubernetes nginx ingress controller I googled openresty for status 431 but didn't find a lot. Will keep digging |
@geoffreysamper can you retry your experiment with https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/#proxy-add-original-uri-header set to |
@geoffreysamper I can confirm that only adding
Also, this confirms my initial comment, that this error was returned by your application. To can test this sending a request directly to your app
|
Thx |
@ElvinEfendi can we explain exact code of how to set proxy-add-original-uri-header as "false". Didn't work. Is this correct? |
What keywords did you search in NGINX Ingress controller issues before filing this one?
Is this a BUG REPORT? Yes
NGINX Ingress controller version: 0.25.1
Kubernetes version (use
kubectl version
):Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.2", GitCommit:"66049e3b21efe110454d67df4fa62b08ea79a19b", GitTreeState:"clean", BuildDate:"2019-05-16T16:23:09Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.10-eks-5ac0f1", GitCommit:"5ac0f1d9ab2c254ea2b0ce3534fd72932094c6e1", GitTreeState:"clean", BuildDate:"2019-08-20T22:39:46Z", GoVersion:"go1.11.13", Compiler:"gc", Platform:"linux/amd64"}
Environment:
uname -a
):What happened:
logs.txt
en defining an ingress for a specific pod and requesting it via a largeurl +/- 4000 chars. a response with status 431 request header fields too large returned
After adding follow annotations on the ingress or changing it via config map it still returned error 431
response headers*
HTTP/1.1 431 Request Header Fields Too Large
Server: openresty/1.15.8.1
Date: Tue, 24 Sep 2019 07:40:24 GMT
How to reproduce it (as minimally and precisely as possible):
I create a small github sample https://github.com/geoffreysamper/simple-site see read me
The text was updated successfully, but these errors were encountered: