You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2021/04/29 13:51:59 UTC
[GitHub] [apisix] eavesmy opened a new issue #4162: request help: upstream sent too big header while reading response header from upstream
eavesmy opened a new issue #4162:
URL: https://github.com/apache/apisix/issues/4162
### upstream 返回超大的 HTTP 头信息时报错
```upstream-sent-too-big-header-while-reading-response-header-from-upstream```
请问我需要更改什么设置？
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] spacewander closed issue #4162: request help: upstream sent too big header while reading response header from upstream
Posted by GitBox <gi...@apache.org>.
spacewander closed issue #4162:
URL: https://github.com/apache/apisix/issues/4162
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] eavesmy commented on issue #4162: request help: upstream sent too big header while reading response header from upstream
Posted by GitBox <gi...@apache.org>.
eavesmy commented on issue #4162:
URL: https://github.com/apache/apisix/issues/4162#issuecomment-829862124
I edit apisix config file like this:
```
nginx_config: # config for render the template to genarate nginx.conf
error_log: "logs/error.log"
error_log_level: "warn" # warn,error
worker_rlimit_nofile: 20480 # the number of files a worker process can open, should be larger than worker_connections
event:
worker_connections: 10620
http:
access_log: "logs/access.log"
keepalive_timeout: 60s # timeout during which a keep-alive client connection will stay open on the server side.
client_header_timeout: 60s # timeout for reading client request header, then 408 (Request Time-out) error is returned to the client
client_body_timeout: 60s # timeout for reading client request body, then 408 (Request Time-out) error is returned to the client
send_timeout: 10s # timeout for transmitting a response to the client.then the connection is closed
underscores_in_headers: "on" # default enables the use of underscores in client request header fields
real_ip_header: "X-Real-IP" # http://nginx.org/en/docs/http/ngx_http_realip_module.html#real_ip_header
real_ip_from: # http://nginx.org/en/docs/http/ngx_http_realip_module.html#set_real_ip_from
- 127.0.0.1
- 'unix:'
proxy_busy_buffers_size: 512k
proxy_buffers: 4 512k
proxy_buffer_size: 256k
#lua_shared_dicts: # add custom shared cache to nginx.conf
# ipc_shared_dict: 100m # custom shared cache, format: `cache-key: cache-size`
````
But dose not work.
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] spacewander commented on issue #4162: request help: upstream sent too big header while reading response header from upstream
Posted by GitBox <gi...@apache.org>.
spacewander commented on issue #4162:
URL: https://github.com/apache/apisix/issues/4162#issuecomment-829957527
You need to configure http_server_configuration_snippet, see https://github.com/apache/apisix/blob/master/docs/en/latest/customize-nginx-configuration.md
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] tokers commented on issue #4162: request help: upstream sent too big header while reading response header from upstream
Posted by GitBox <gi...@apache.org>.
tokers commented on issue #4162:
URL: https://github.com/apache/apisix/issues/4162#issuecomment-829740293
The upstream response header will be saved to the first buffer, which size is controlled by `proxy_buffer_size` directive.
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] Firstsawyou commented on issue #4162: request help: upstream sent too big header while reading response header from upstream
Posted by GitBox <gi...@apache.org>.
Firstsawyou commented on issue #4162:
URL: https://github.com/apache/apisix/issues/4162#issuecomment-829288001
You can try to set the configuration information of `proxy_busy_buffers_size`, `proxy_buffers` and · `proxy_busy_buffers_size` through [customize-nginx-configuration](https://github.com/apache/apisix/blob/master/docs/en/latest/customize-nginx-configuration.md) method.
https://www.cyberciti.biz/faq/nginx-upstream-sent-too-big-header-while-reading-response-header-from-upstream/
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] eavesmy commented on issue #4162: request help: upstream sent too big header while reading response header from upstream
Posted by GitBox <gi...@apache.org>.
eavesmy commented on issue #4162:
URL: https://github.com/apache/apisix/issues/4162#issuecomment-838356417
> You need to configure http_server_configuration_snippet, see https://github.com/apache/apisix/blob/master/docs/en/latest/customize-nginx-configuration.md
Thx.
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org