D-Brio7 opened a new issue, #11726:
URL: https://github.com/apache/apisix/issues/11726
### Description
Given these configuration's in apisix helm chart in configmap.yaml to
modify nginx buffer limits
large_client_header_buffers: 64 512k
client_header_buffer_size: 1050m
proxy_buffer_size: 256k
proxy_buffers: 4 256k
proxy_busy_buffers_size: 256k
client_body_buffer_size: 1050m
Below is the error snippet :-
2024/11/08 07:29:32 [error] 50#50: *101493 upstream sent too big header
while reading response header from upstream, client: 172.26.134.5, server: _,
request: "GET
/oauth2/callback?state=eyJhbGciOiJIUzI1NiJ9.eyJhdWQiOlsidHJpbm9fb2F1dGhfdWkiXSwiZXhwIjoxNzMxMDUxODY0fQ.52_TinuNqd51GApHdP-ea5GVunKMwtlgPXUztml-BGE&session_state=9160d6f6-aa00-4178-8bd2-2c8abe26b5d1&iss=https%3A%2F%2Fdev-example.test.com%2Frealms%2Ftrino&code=6c2bf143-3a13-4c8f-b738-39eb3f7ea6d5.9160d6f6-aa00-4178-8bd2-2c8abe26b5d1.dea871b5-1073-46ce-ada0-81a79807e044
HTTP/2.0", upstream:
"https://172.26.134.47:443/oauth2/callback?state=eyJhbGciOiJIUzI1NiJ9.eyJhdWQiOlsidHJpbm9fb2F1dGhfdWkiXSwiZXhwIjoxNzMxMDUxODY0fQ.52_TinuNqd51GApHdP-ea5GVunKMwtlgPXUztml-BGE&session_state=9160d6f6-aa00-4178-8bd2-2c8abe26b5d1&iss=https%3A%2F%2Fdev-keycloak.crisil.local%2Frealms%2Ftrino&code=6c2bf143-3a13-4c8f-b738-39eb3f7ea6d5.9160d6f6-aa00-4178-8bd2-2c8abe26b5d1.dea871b5-1073-46ce-ada0-81a79807e044";,
host: "dev-example.test.com"
### Environment
- APISIX version (run `apisix version`): 3.11.0
- Operating system (run `uname -a`): Linux
- OpenResty / Nginx version (run `openresty -V` or `nginx -V`): 1.25.3.2
- etcd version, if relevant (run `curl
http://127.0.0.1:9090/v1/server_info`): 3.5.0
- 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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
