-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
request help: upstream sent too big header while reading response header from upstream #4162
Comments
You can try to set the configuration information of |
The upstream response header will be saved to the first buffer, which size is controlled by |
I edit apisix config file like this:
But dose not work. |
You need to configure http_server_configuration_snippet, see https://github.com/apache/apisix/blob/master/docs/en/latest/customize-nginx-configuration.md |
Thx. |
I have solved this problem。Please look at here! Error Info:
The problem I have is that the response size is 5kb,bigger than proxy_buffer_size size,which default is 4kb. This leads to API SIX reporting 502 error. proxy_buffer_size: Solution:change the nginx proxy_buffer_size size to the right size. so we modify the /conf/config.yaml,and add the some snippets,like this:
The http_configuration_snippet and http_server_configuration_snippet will attach to the nginx.conf,which the options from conf/config-default.yaml and /conf/config.yaml. If you want to learn more about how the http_configuration_snippet and http_server_configuration_snippet works,look at |
i am still facing problem with this. upstream sent too big header while reading response header from upstream, client: 172.18.0.1, tried below in docker compose and no luck apisix: cloning api docker and modifying conf/conf.yaml file sound tedious task. appreciate help guys. :) |
upstream 返回超大的 HTTP 头信息时报错
upstream-sent-too-big-header-while-reading-response-header-from-upstream
请问我需要更改什么设置?
The text was updated successfully, but these errors were encountered: