Skip to content

Conversation

@timmc
Copy link

@timmc timmc commented Jan 3, 2026

Proposed changes

This clarifies the interaction of proxy_buffer_size and response headers. When the buffer size is too small for the response headers, nginx returns a 502 and logs "upstream sent too big header while reading response header from upstream".

Reference: https://github.com/nginx/nginx/blob/6a67f71a4a78edb662c190af93ac6d3d680e107a/src/http/ngx_http_upstream.c#L2547

Checklist

Before creating a PR, run through this checklist and mark each as complete:

This clarifies the interaction of `proxy_buffer_size` and response headers.
When the buffer size is too small for the response headers, nginx returns
a 502 and logs "upstream sent too big header while reading response header
from upstream".

Reference: https://github.com/nginx/nginx/blob/6a67f71a4a78edb662c190af93ac6d3d680e107a/src/http/ngx_http_upstream.c#L2547
@timmc
Copy link
Author

timmc commented Jan 3, 2026

I have hereby read the F5 CLA and agree to its terms

@timmc
Copy link
Author

timmc commented Jan 3, 2026

FYI, the PR template has a broken link to the contribution guidelines. I believe it's meant to link to https://github.com/f5/f5-cla/blob/main/CONTRIBUTING.md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant