Nginx proxy_buffer_size to solve the back-end service transmission data too much, in fact, the header is too big problem

Nginx proxy_buffer_size to solve the back-end service transmission data too much, in fact, the header is too big problem

These three parameters have been set to fix the amount

Proxy_buffer_size 64k;
Proxy_buffers   4 32k;
Proxy_busy_buffers_size 64k;

In the spirit of excellence I turned the official website
Official website explanation

In general, I still do not understand. I put out the error message and need it later.
Development said nginx502, back-end access to Jesery no problem

No
, Curl-i-V "test.lebi.letv.cn/report/rest/saiku/api/query/7c53220d-a870-1fe3-9353-4a6f967f25cb/result/ Metadata/hierarchies/%5bdm_rec. Dim_live_station%5d.%5bdm_rec. Dim_live_station. Live_station_name%5d/levels/dm_rec. Dim_live_station. live_station_name?result=false&_=1489736122190 "
can
Curl-i-V" http://10.142.165.45:8080/report/rest/ Saiku/api/query/7c53220d-a870-1fe3-9353-4a6f967f25cb/result/metadata/hierarchies/%5bdm_rec. Dim_live_station%5d.%5bdm_rec. Dim_live_station. Live_station_name%5d/levels/dm_rec. Dim_live_station. live_station_name?result=false&_=1489736122190 "

Log comparison

Return 502 "10.73.137.12", "[17/mar/2017:16:32:08 +0800]", "http/1.1", "-", "GET", "/report/rest/saiku/api/query/ 7c53220d-a870-1fe3-9353-4a6f967f25cb/result/metadata/hierarchies/%5bdm_rec. Dim_live_station%5d.%5bdm_rec. Dim_live_station. Live_station_name%5d/levels/dm_rec. Dim_live_station. live_station_name?result=false&_=1489736122190 "," 502 "," http://test.lebi.letv.cn/report/rest/saiku/api/ Query/7c53220d-a870-1fe3-9353-4a6f967f25cb/result/metadata/hierarchies/%5bdm_rec. Dim_live_station%5d.%5bdm_rec. Dim_live_station. Live_station_name%5d/levels/dm_rec. Dim_live_station. live_station_name?result=false&_=1489736122190 "," 172 "," 0.157 "," 10.142.165.45:8080 ","-"," curl/7.35.0 "," 0.157 "," 329 "," 328 "normal" 10.73.137.12 "," [17/mar/2017:16:32:47 +0800] "," http/1.1 ","-"," GET ","/report/rest/saiku/api /query/7c53220d-a870-1fe3-9353-4a6f967f25cb/result/metadata/hierarchies/%5bdm_rec. Dim_live_station%5d.%5bdm_rec. Dim_live_station. Live_station_name%5d/levels/dm_rec. Dim_live_station. Live_station_name?result=false&_=1489736122190 "," http://test.lebi.letv.cn/report/rest/saiku/api/query/"," 7c53220d-a870-1fe3-9353-4a6f967f25cb/result/metadata/hierarchies/%5bdm_rec. Dim_live_station%5d.%5bdm_rec. Dim_live_station. Live_station_name%5d/levels/dm_rec. Dim_live_station. live_station_name?result=false&_=1489736122190 "," 1342118 "," 4.350 "," 10.142.165.45:8080 ","-"," curl/7.35.0 ","
 0.180 "," 329 "," 1346306 "

I measured the JSON data returned about 1.3M, maybe the return value is too large, exceeding the threshold, but more than which, more tangled.

View the error log to get upstream sent too big header while reading response headers from upstream, saying the header is too big. Well, learn the next header.

2017/03/17 16:32:08 [ERROR] 17441#0: *403548696 upstream sent too big header while reading Respon Se header from upstream, client:10.73.137.12, server:test.lebi.letv.cn, request: "get/report/rest/saiku/api/query/ 7c53220d-a870-1fe3-9353-4a6f967f25cb/result/metadata/hierarchies/%5bdm_rec. Dim_live_station%5d.%5bdm_rec. Dim_live_station. Live_station_name%5d/levels/dm_rec. Dim_live_station. live_station_name?result=false&_=1489736122190 http/1.1 ", Upstream:" http://10.142.165.45:8080/report/rest/ Saiku/api/query/7c53220d-a870-1fe3-9353-4a6f967f25cb/result/metadata/hierarchies/%5bdm_rec. Dim_live_station%5d.%5bdm_rec. Dim_live_station. Live_station_name%5d/levels/dm_rec. Dim_live_station. live_station_name?result=false&_=1489736122190 ", Host:" Test.lebi.letv.cn "