-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
400 Request Header Or Cookie Too Large #9834
Comments
@francoeder Can you paste the exact route and upstream configuration that you have configured? Also share the logs from access.log and error.log, if any. |
The requested information is below. Route configuration
Upstream configuration
Note: The access.log and error.log files show nothing different after executing the offending request ( Thanks in advance for the help! |
I managed to solve the problem. This thread helped me 👉 #6296 I needed to configure a proxy-rewrite plugin in my route, considering the domain of my API (Same domain used in the upstream) and Voilà! I was able to consume my API via APISIX Api Gateway. I hope it helps someone in the future. |
@francoeder You can close this issue. Thanks |
Because APISIX uses nginx under the hood, i solved it by adding this to my config.yml nginx_config:
http_server_configuration_snippet: |
large_client_header_buffers 4 32k; |
am still getting 400 Request Header Or Cookie Too Large even after putting above changes |
Description
I'm in my first steps with Apache APISIX.
I just followed the step by step contained in this page apisix-workshop, promoted by Bobur Umurzokov.
What did I do:
However, when invoking a GET request for the mapped route, I get the error "400 Request Header Or Cookie Too Large".
curl -i -X GET "http://127.0.0.1:9080/api/v1/conteudos"
Can anyone help me?
Environment
apisix version
): 2.13.1uname -a
): Windowsopenresty -V
ornginx -V
): ???curl http://127.0.0.1:9090/v1/server_info
): 3.4.15luarocks --version
): -The text was updated successfully, but these errors were encountered: