I have upgraded ingress-nginx-controller from v1.9.4 to v1.11.5 and kubewebhook from v20231011-8b53cabe0 to v20231226-1a7112e06. I am able to hit urls of api and can see them in logs but when I am trying to hit gui(frontend) search, I am getting :
error- upstream sent duplicate header line: "Transfer-Encoding: chunked", previous value: "Transfer-Encoding: chunked" while reading response header from upstream
I have tried upgrading ingress-nginx-controller v1.12.1 but I'm facing the same error :
error-upstream sent duplicate header line: "Transfer-Encoding: chunked", previous value: "Transfer-Encoding: chunked" while reading response header from upstream
I have upgraded ingress-nginx-controller from v1.9.4 to v1.11.5 and kubewebhook from v20231011-8b53cabe0 to v20231226-1a7112e06. I am able to hit urls of api and can see them in logs but when I am trying to hit gui(frontend) search, I am getting :
error- upstream sent duplicate header line: "Transfer-Encoding: chunked", previous value: "Transfer-Encoding: chunked" while reading response header from upstream
I have tried upgrading ingress-nginx-controller v1.12.1 but I'm facing the same error :
Share Improve this question edited Apr 1 at 8:16 Alan Finiti 6710 bronze badges asked Apr 1 at 7:28 user30128323user30128323 12 bronze badges New contributor user30128323 is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct.error-upstream sent duplicate header line: "Transfer-Encoding: chunked", previous value: "Transfer-Encoding: chunked" while reading response header from upstream
1 Answer
Reset to default 0Try checking the Ingress Annotations
Add the following annotations to your ingress resource:
nginx.ingress.kubernetes.io/proxy-buffering: "off"
nginx.ingress.kubernetes.io/configuration-snippet: |
proxy_set_header Transfer-Encoding "";
This prevents nginx from interfering with the Transfer-Encoding header.