Please use this template for troubleshooting questions.
My issue: 2025/12/10 21:54:40 [error] 36#36: *11 upstream sent too big header while reading response header from upstream
How I encountered the problem: I have installed v2.2.2 of nginx-gateway-fabrix as part of ingress controller replacement
Solutions I’ve tried: I have tried updating the annotations but looks like it is not supported
Version of NGF and/or NGINX:v2.2.2 and 1.3.0
Deployment environment: Dev Environment
Hey @khannasumit961 can you tell me which annotation are you trying to add on the NGF side to increase your response buffers?
annotations:
nginx.org/http-snippets: |
Hi,
I am getting this error:
2025/12/10 21:54:40 [error] 36#36: *11 upstream sent too big header while reading response header from upstream,
proxy_buffer_size 32k;
proxy_buffers 8 32k;
proxy_busy_buffers_size 64k;
large_client_header_buffers 4 32k;
okay great. You can add these to specific server, location, http blocks using SnippetsFilter API. Let me know if it fixes things for you
Just a quick note to add, we are planning a ProxySettingsPolicy CRD early next year specifically for proxy buffers and other directives that are popular (proxy_*): Design ProxySettingsPolicy API · Issue #4067 · nginx/nginx-gateway-fabric · GitHub
SnippetsFilter should allow you to achieve this for now though,
Hey @salonichf5 Could you please guide me how can i achieve this in httproute or gateway? I would really appreciate your help!
Just want to summarize, snippetsFilter worked for @khannasumit961 after upgrading his helm installation with --set nginxGateway.snippetsFilters.enable=true .
snippetsFilters is disabled by default, so make sure to set this flag during install/upgrade.
Thanks a lot @salonichf5 . You were a great help! Big shout out to you! Great work y’all!
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.