Welcome! Log In Create A New Profile

Advanced

Re: How to fix ERR_RESPONSE_HEADERS_TRUNCATED error

Francis Daly
March 15, 2020 09:30AM
On Sun, Mar 15, 2020 at 09:02:28AM -0400, bubunia2000ster wrote:

Hi there,

> User<URL in Chrome with https> ->AWS Route 53(DNS resolution) -> AWS NLB
> (443)-> nginx(implements path based routing to different backend EC2
> instances)------->http(backend ec2 instances)

That says "the plan is http from nginx to backend".

> SSL is terminated at the nginx. When I run directly this URL with
> https://<domain name>:6667 it works fine and page loads properly. But

That says "it works using https to backend".

> upstream app1_external {
> sticky name=srv_id expires=1h domain=<domain-Name> httponly secure path=/;
> keepalive 16;
> server test1.example.com:6667 max_fails=2 fail_timeout=300s;server
> test2.example.com:6667 max_fails=2 fail_timeout=300s;
> }

The backend is port 6667, as above.

> location /rest/ {
> proxy_pass http://app1_external/;

And you try to talk http to it.

> nginx version: nginx/1.13.5
> Can anyone help me in this regard how to fix this issue?

Either - make your port 6667 listener use http, not https; or tell nginx
to talk https to it.

f
--
Francis Daly francis@daoine.org
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

How to fix ERR_RESPONSE_HEADERS_TRUNCATED error

bubunia2000ster March 15, 2020 09:02AM

Re: How to fix ERR_RESPONSE_HEADERS_TRUNCATED error

Francis Daly March 15, 2020 09:30AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 76
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready