简体   繁体   English

k8s NGINX 入口控制器上的请求失败,并显示“从上游读取响应标头时上游发送的标头太大”

[英]Request on k8s NGINX ingress controller fails with “upstream sent too big header while reading response header from upstream”

When I try to send a request through my NGINX ingress with headers larger than 4k, it returns a 502 error:当我尝试通过标头大于 4k 的 NGINX 入口发送请求时,它返回 502 错误:

[error] 39#39: *356 upstream sent too big header while reading response header from upstream, 
    client: <ip>,
    server: <server>, 
    request: "GET /path/ HTTP/1.1", 
    subrequest: "/_external-auth-Lw", 
    upstream: "<uri>", 
    host: "<host>"
[error] 39#39: *356 auth request unexpected status: 502 while sending to client, 
    client: <ip>, 
    server: <server>, 
    request: "GET /path/ HTTP/1.1", 
    host: "<host>"

I've followed instructions about how to allegedly resolve this issue by configuring the proxy-buffer-size in the ingress controller ( nginx.ingress.kubernetes.io/proxy-buffer-size: "16k" ), but it doesn't seem to work.我已按照有关如何通过在入口控制器( nginx.ingress.kubernetes.io/proxy-buffer-size: "16k" )中配置proxy-buffer-size来解决此问题的说明进行操作,但似乎没有上班。 The only thing that I can think of, is that it has something to do with the proxy-buffer-size of the subrequest, which doesn't seem to get set.我唯一能想到的是,它与子请求的proxy-buffer-size有关,它似乎没有设置。

The proxy_buffering header wasn't being set on the /_external-auth-Lw endpoint in the NGINX config.在 NGINX 配置中的 /_external-auth-Lw 端点上未设置 proxy_buffering 标头。 Issue has been resolved as of v. 0.14.0.从 v. 0.14.0 开始,问题已得到解决。

暂无
暂无

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 Nginx上游在从上游读取响应头时发送了太大的头 - Nginx upstream sent too big header while reading response header from upstream 上游从客户端,客户端(nginx,清漆)读取响应头时发送了太大的头 - upstream sent too big header while reading response header from upstream, client (nginx, varnish) Nginx Web 服务器错误 - 从上游读取响应标头时,上游发送的标头太大 - Nginx Web Server Error - upstream sent too big header while reading response header from upstream 上游从上游读取响应头时发送了太大的头 - upstream sent too big header while reading response header from upstream 在 Keycloak 中读取来自上游的响应 header 时,上游发送了太大的 header - Upstream sent too big header while reading response header from upstream in Keycloak 如何修复上游从上游读取响应头时发送过大的头? - how to fix upstream sent too big header while reading response header from upstream? 从上游读取响应标头时,上游发送了太大的标头 - upstream sent too big header while reading response header from upstream Laravel Valet/Nginx: 502 Bad Gateway: 93883#0: *613 上游发送过大 - Laravel Valet/Nginx: 502 Bad Gateway: 93883#0: *613 upstream sent too big header while reading response header from upstream, client: 127.0.0.1 上游在访问https域时从上游读取响应头时没有发送有效的HTTP / 1.0头 - upstream sent no valid HTTP/1.0 header while reading response header from upstream when access https domain PHP 升级后的 nginx 错误:FastCGI 在 stderr 中发送:“”同时从上游读取响应标头 - nginx error after PHP upgrade: FastCGI sent in stderr: " " while reading response header from upstream
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM