HTTP Status 400 – Bad Request in API call
SagarJagtap26 opened this issue · 3 comments
Dear All,
Currently we are facing one nginx ingress controller issue where GET API call is throwing HTTP Status 400 – Bad Request error
<!doctype html><title>HTTP Status 400 – Bad Request</title><style type="text/css">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style>
HTTP Status 400 – Bad Request
We have added below parameters into the config map of ingress controller
data:
allow-snippet-annotations: "true"
client_header_buffer_size: 64k
http2-max-field-size: 16k
http2-max-header-size: 128k
large-client-header-buffers: 4 64k
proxy-buffer-size: 128k
proxy-buffers: 4 256k
proxy-busy-buffers-size: 256k
server-name-hash-bucket-size: "128"
and ingress annotations are updated with below Parameters
metadata:
annotations:
kubernetes.io/ingress.class: nginx-fdfd
meta.helm.sh/release-name: ddfdfdf
meta.helm.sh/release-namespace: asddd
nginx.ingress.kubernetes.io/client-body-buffer-size: 64k
nginx.ingress.kubernetes.io/client-header-buffer-size: 128k
nginx.ingress.kubernetes.io/http2-max-header-size: 96k
nginx.ingress.kubernetes.io/large-client-header-buffers: 4 128k
nginx.ingress.kubernetes.io/server-snippet: |
client_header_buffer_size 128k;
large_client_header_buffers 4 128k;
Logs
[06/Nov/2024:12:00:00 +0000] "GET /v4/resource?id=0000000000000&relatedParty.id=0000&resourceSpecification.referredType=All HTTP/1.1" 400 435 "
https://******************/"
"Synapse-PT-HttpComponents-NIO" 9137 0.001
It would be great help if you could suggest some other changes are required to solve this issue please...
This issue is currently awaiting triage.
If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members by writing /triage accepted in a comment.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
/remove-kind bug
The information you have posted is not enough to base any useful comments on.
The template of a new bug report asks questions and answering those questions puts data here that can be analyzed and commented on. So please look at the template of a new bug report and then edit this issue description with answers to those questions, in markdown format.
After you have provided the useful required information, then you can reopen the issue. Because without action items, there is nothing to track here and it just adds to the tally of open issues.
/close
@longwuyuan: Closing this issue.
In response to this:
/remove-kind bug
The information you have posted is not enough to base any useful comments on.
The template of a new bug report asks questions and answering those questions puts data here that can be analyzed and commented on. So please look at the template of a new bug report and then edit this issue description with answers to those questions, in markdown format.
After you have provided the useful required information, then you can reopen the issue. Because without action items, there is nothing to track here and it just adds to the tally of open issues.
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.