Yes the answer is on the elastic load balancer you must use protocol TCP or
SSL - not HTTP or HTTPS. The HTTP/HTTPS listeners keep the connections open
for reuse
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,237386,264196#msg-264196
___
Hi! Thanks for replying. It appears the issue might actually be on the AWS
side. AWS is looking into it. Think its an issue with the elastic load
balancer.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,237386,260318#msg-260318
___
nginx mail
I also just tested regular http and it is having the same problem.
dgobaud Wrote:
---
> Don't think so - config is below and the relevant url is
> /dashboard_stream
>
> upstream my_app {
> server unix:///var/
proxy_cache off;
proxy_http_version 1.1;
}
}
Valentin V. Bartenev Wrote:
---
> On Monday 13 July 2015 12:02:44 dgobaud wrote:
> > Any update on this? Seeing this problem with nginx leaving
> connections open
Hi, I'm using AWS Beanstalk with nginx in front of a Puma server serving
Ruby on Rails. I have one URL that is for an EventSource so it is kept alive
and data is streamed out. I was running into this problem
http://forum.nginx.org/read.php?2,237386,237386 where when the client closes
the browser bu
Any update on this? Seeing this problem with nginx leaving connections open
on AWS Beanstalk using nginx to proxy to puma/ruby on rails.
nginx version: nginx/1.6.2
NAME="Amazon Linux AMI"
VERSION="2015.03"
ID="amzn"
ID_LIKE="rhel fedora"
VERSION_ID="2015.03"
PRETTY_NAME="Amazon Linux AMI 2015.03"
