Skip to content
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.

Sign up for GitHub

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

Jump to bottom

HTTP Status 400 – Bad Request in API call #12329

Closed
SagarJagtap26 opened this issue Nov 7, 2024 · 3 comments
Closed

HTTP Status 400 – Bad Request in API call #12329

SagarJagtap26 opened this issue Nov 7, 2024 · 3 comments
Labels
needs-kind Indicates a PR lacks a `kind/foo` label and requires one. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@SagarJagtap26
Copy link

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...
@SagarJagtap26 SagarJagtap26 added the kind/bug Categorizes issue or PR as related to a bug. label Nov 7, 2024
@k8s-ci-robot
Copy link
Contributor

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.

@k8s-ci-robot k8s-ci-robot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority labels Nov 7, 2024
@longwuyuan
Copy link
Contributor

/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

@k8s-ci-robot k8s-ci-robot added needs-kind Indicates a PR lacks a `kind/foo` label and requires one. and removed kind/bug Categorizes issue or PR as related to a bug. labels Nov 7, 2024
@k8s-ci-robot
Copy link
Contributor

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
needs-kind Indicates a PR lacks a `kind/foo` label and requires one. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
[SIG Network] Ingress NGINX
Status: Done
Milestone
No milestone
Development

No branches or pull requests
3 participants
@longwuyuan @k8s-ci-robot @SagarJagtap26