Nginx 502 error upstream sent too big header while reading response headers from upstream

Source: Internet
Author: User

The original setting is

Proxy_buffer_size 4k;

Proxy_buffers 4 32k;

Proxy_busy_buffers_size 64k;

In this configuration, using Fiddler for packet Analysis, it is found that as long as the size of the requested header is greater than 4378 bytes when the report 502, when the header is 4377 and below the time normal.

Change the configuration to:

Proxy_buffer_size 64k;
Proxy_buffers 32k;
Proxy_busy_buffers_size 128k;

After that, it's normal.

PS: Check the official and some of the network data, found that the buffer is used to buffer the response of the upstream (back-end) server, there is no data to find that it is also the size of the request header will have an impact. However, the problem that is currently encountered is due to the large size of the requested header. This question mark a moment.

Nginx 502 error upstream sent too big header while reading response headers from upstream

Related Article

E-Commerce Solutions

Leverage the same tools powering the Alibaba Ecosystem

Learn more >

Apsara Conference 2019

The Rise of Data Intelligence, September 25th - 27th, Hangzhou, China

Learn more >

Alibaba Cloud Free Trial

Learn and experience the power of Alibaba Cloud with a free trial worth $300-1200 USD

Learn more >

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: and provide relevant evidence. A staff member will contact you within 5 working days.