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
___
Any update on this issue? Is there a fix I can apply on the AWS side?
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,237386,264195#msg-264195
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
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
Hello!
On Tue, Jul 14, 2015 at 12:43:53PM -0400, dgobaud wrote:
> I also just tested regular http and it is having the same problem.
First of all, please clarify what's the problem you are seeing.
That is, please provide details/stats/logs that show the problem.
--
Maxim Dounin
http://nginx.
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/run/puma/my_app.sock;
>
Don't think so - config is below and the relevant url is /dashboard_stream
upstream my_app {
server unix:///var/run/puma/my_app.sock;
}
server {
listen 80;
server_name _ localhost; # need to listen to localhost for worker
tier
if ($http_x_forward
On Monday 13 July 2015 12:02:44 dgobaud wrote:
> Any update on this? Seeing this problem with nginx leaving connections open
> on AWS Beanstalk using nginx to proxy to puma/ruby on rails.
[..]
Do you have cache or proxy store configured?
wbr, Valentin V. Bartenev
__
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"
1. Where can i get a full list of these disabled headers:
"By default, nginx does not pass the header fields “Date”, “Server”,
“X-Pad”, and “X-Accel-...” from the response of a proxied server to a
client. The proxy_hide_header directive sets additional fields that will not
be passed. If, on the co
On Monday 19 May 2014 17:32:07 newnovice wrote:
> I tried with: "proxy_pass_header Connection;" -- which
> should do this according to documentation: "Permits passing otherwise
> disabled header fields from a proxied server to a client."
> (from upstream_server to client)
No, it
I tried with: "proxy_pass_header Connection;" -- which
should do this according to documentation: "Permits passing otherwise
disabled header fields from a proxied server to a client."
(from upstream_server to client)
But this did not pass thru the Connection header coming from t
thanks/
use the lua-module
it is possible?
19.05.2014 18:47, Valentin V. Bartenev пишет:
I can try by using combination of add_header and $upstream_http_* variables.
Also, some headers can be preserved by the proxy_pass_header directive.
___
nginx
On Saturday 17 May 2014 11:28:33 newnovice wrote:
> Can I proxy_pass on the way back also - and preserve all headers coming from
> the upstream service?
>
I can try by using combination of add_header and $upstream_http_* variables.
Also, some headers can be preserved by the proxy_pass_header dir
Can I proxy_pass on the way back also - and preserve all headers coming from
the upstream service?
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,237386,250172#msg-250172
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman
On Friday 16 May 2014 18:32:32 newnovice wrote:
> Does this also affect a 'Connection Close' header coming from the upstream
> service - being sent as a connect-keep-alive to the requesting client thru
> my nginx ssl reverse proxy?
>
> (I am trying to setup nginx as an SSL proxy; when the upstrea
Does this also affect a 'Connection Close' header coming from the upstream
service - being sent as a connect-keep-alive to the requesting client thru
my nginx ssl reverse proxy?
(I am trying to setup nginx as an SSL proxy; when the upstream service sends
a connection close I want this to be passe
Ubuntu 12.04 + Nginx 1.4.7
I'm not 100% sure this is the same issue, but the symptoms are the same.
Nginx as SSL termination to an eventsource backend upstream. Nginx
active connections continuously go up until a restart.
I just upgraded to 1.6.0 to see if it resolves the issue.
Thanks for you
On Tuesday 13 May 2014 00:46:37 Peter B. wrote:
> We're affected by this issue as well. Is there an open ticket where we
> can track progress at http://trac.nginx.org/?
What version of nginx and what operating system do you use?
Nginx 1.5.5+ has been able to reliably detect close of connection
on
We're affected by this issue as well. Is there an open ticket where we
can track progress at http://trac.nginx.org/?
--
Posted via http://www.ruby-forum.com/.
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hello!
On Tue, Jul 23, 2013 at 10:06:09AM +1000, Robert Mueller wrote:
>
> > > Yes, I haven't heard in a while what the status of this is. I'm
> > > currently using our existing patch, but would love to drop it and
> > > upgrade when it's included in nginx core...
> >
> > As far as I can tell t
> > Yes, I haven't heard in a while what the status of this is. I'm
> > currently using our existing patch, but would love to drop it and
> > upgrade when it's included in nginx core...
>
> As far as I can tell the state is roughly the same (though patch
> in question improved a bit). Valentin?
Hello!
On Tue, Jul 09, 2013 at 12:52:24PM +1000, Robert Mueller wrote:
>
> > I have the same problem. I really need this feature. how is this going?
> >
> > >> Maxim Dounin:
> > > Valentin is already worked on this, and I believe he'll be able to
> > > provide a little bit more generic patch.
>
> I have the same problem. I really need this feature. how is this going?
>
> >> Maxim Dounin:
> > Valentin is already worked on this, and I believe he'll be able to
> > provide a little bit more generic patch.
>
> does this mean in the future we can use epoll to detect the client
> connection'
Hi everyone,
I have the same problem. I really need this feature. how is this going?
>> Maxim Dounin:
> Valentin is already worked on this, and I believe he'll be able to
> provide a little bit more generic patch.
does this mean in the future we can use epoll to detect the client
connection's a
> Valentin is already worked on this, and I believe he'll be able to
> provide a little bit more generic patch.
Ok, well I might just use ours for now, but won't develop it any
further.
Any idea on a time frame for this more official patch?
Rob
___
Hello!
On Tue, Mar 19, 2013 at 03:45:10PM +1100, Robert Mueller wrote:
>
> > > When an https client drops it's connection, the upstream http proxy
> > > connection is not dropped. If nginx can't detect an https client
> > > disconnect properly, that must mean it's leaking connection information
> > When an https client drops it's connection, the upstream http proxy
> > connection is not dropped. If nginx can't detect an https client
> > disconnect properly, that must mean it's leaking connection information
> > internally doesn't it?
>
> No. It just can't say if a connection was closed
Hello!
On Sat, Mar 16, 2013 at 09:32:27AM +1100, Robert Mueller wrote:
>
> > In case of https, in many (most) cases there are pending data -
> > due to various SSL packets send during connection close. This
> > means connection close detection with https doesn't work unless
> > you use kqueu
> In case of https, in many (most) cases there are pending data -
> due to various SSL packets send during connection close. This
> means connection close detection with https doesn't work unless
> you use kqueue.
>
> Further reading:
>
> http://mailman.nginx.org/pipermail/nginx/2011-June/02
Hello!
On Fri, Mar 15, 2013 at 03:22:31PM +1100, Robert Mueller wrote:
[...]
> When using http with my test client, I see this in the nginx log when
> the client disconnects:
>
> 2013/03/14 23:27:27 [info] 27717#0: *1 client prematurely closed
> connection, so upstream connection is closed too
Hi
I'm trying to setup nginx to proxy a server sent events connection
(http://dev.w3.org/html5/eventsource/) to a backend server.
The approach is the browser connects to a particular path, which then
checks the cookies to see the connection is authorised, and then returns
an X-Accel-Redirect head
31 matches
Mail list logo
