Deepak-0822 opened a new issue, #12572: URL: https://github.com/apache/apisix/issues/12572
### Description Hi team, Initernally i faced a 500 internal server error, so I recently updated the APISIX Ingress Controller image to 2.0.0-rc3 and the APISIX image to 3.13.0-ubuntu. After the upgrade, 500 internal server error is fixed now I am encountering the following error: "400 Bad Request Request Header Or Cookie Too Large: I tried modifying the NGINX configuration by setting large_client_header_buffers 4 32k, but it resulted in a 500 Internal Server Error. I had to revert the change to restore functionality. Could someone help me with this issue? I need to resolve it before moving to production. I’ve attached the latest logs from the Admin APISIX and APISIX Ingress Controller. Please let me know if you notice anything suspicious or if I should adjust any specific configuration. [apisix-admin-logs.txt](https://github.com/user-attachments/files/22073367/apisix-admin-logs.txt) [apisix-ingress-contrller-logs.txt](https://github.com/user-attachments/files/22073366/apisix-ingress-contrller-logs.txt) ### Environment - APISIX version (run `apisix version`): - Operating system (run `uname -a`): - OpenResty / Nginx version (run `openresty -V` or `nginx -V`): - etcd version, if relevant (run `curl http://127.0.0.1:9090/v1/server_info`): - APISIX Dashboard version, if relevant: - Plugin runner version, for issues related to plugin runners: - LuaRocks version, for installation issues (run `luarocks --version`): -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@apisix.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
