On Mon, Apr 15, 2013 at 6:38 PM, Maxim Dounin wrote:
>
> Hello!
>
> On Mon, Apr 15, 2013 at 06:18:04PM -0400, Richard Stanway wrote:
>
> > Hello,
> > I'm using the limit_req directive to control the rate at which my backends
> > are hit with requests. Typically a backend will generate a page and t
Hello!
On Mon, Apr 15, 2013 at 06:18:04PM -0400, Richard Stanway wrote:
> Hello,
> I'm using the limit_req directive to control the rate at which my backends
> are hit with requests. Typically a backend will generate a page and the
> client will not request anything for a short while, so a rate o
djczaski Wrote:
---
> I've compiled for ARM A8. The biggest issue was configuring to use the
system OpenSSL and pcre libraries. other than that , no problems.
Thanks for the input. By any chance, did you write a tutorial that I could
use to try
Hello,
I'm using the limit_req directive to control the rate at which my backends
are hit with requests. Typically a backend will generate a page and the
client will not request anything for a short while, so a rate of 1 per
second works well. Sometimes however a backend will return a HTTP redirect
Hello!
On Mon, Apr 15, 2013 at 10:42:30PM +0100, Francis Daly wrote:
> On Mon, Apr 15, 2013 at 05:35:27PM -0400, jaychris wrote:
>
> Hi there,
>
> > I was using the X_FORWARDED_PROTO header to make some decisions on the
> > backend when I was using Apache, but it doesn't look like Nginx is han
Thanks! Setting "underscores_in_headers on;" fixed the issue and
X_FORWARDED_PROTO is being carried forward now.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,238384,238387#msg-238387
___
nginx mailing list
nginx@nginx.org
http://mailman.ng
On Mon, Apr 15, 2013 at 05:35:27PM -0400, jaychris wrote:
Hi there,
> I was using the X_FORWARDED_PROTO header to make some decisions on the
> backend when I was using Apache, but it doesn't look like Nginx is handling
> the header currently:
>
> client sent invalid header line: "X_FORWARDED_PR
Running Nginx 1.2.7 behind HAproxy, with SSL being terminated on on HAproxy.
I was using the X_FORWARDED_PROTO header to make some decisions on the
backend when I was using Apache, but it doesn't look like Nginx is handling
the header currently:
client sent invalid header line: "X_FORWARDED_PROTO
Hello!
On Mon, Apr 15, 2013 at 08:08:20PM +0100, Richard Kearsley wrote:
> Hi
> Is the max value specified in `open_file_cache` on a per-worker basis?
> e.g. if I set it to 20,000, will it cache 80,000 open fds with 4 workers?
Yes, it's per-worker.
--
Maxim Dounin
http://nginx.org/en/donation.
Hi
Is the max value specified in `open_file_cache` on a per-worker basis?
e.g. if I set it to 20,000, will it cache 80,000 open fds with 4 workers?
Thanks
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On Sat, Apr 13, 2013 at 10:35:47PM -0400, mastah wrote:
Hi there,
>I've a sub domain which we will call : sub.example.com
>I've an internal application at 127.0.0.1:9090/app
>
> What I would like :
>I would like to proxy sub.example.com to 127.0.0.1:9090/app and i want to
> keep my U
On Sun, Apr 14, 2013 at 10:50:15PM -0400, Ian M. Evans wrote:
Hi there,
> I've realized that it would probably be wise to develop locally by running
> a localhost server in a linux VM on my laptop and desktop.
>
> Can anyone give me any tips (or point me to a tutorial/article) that would
> show
you might want to play with your /etc/hosts.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,238368,238372#msg-238372
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On 9 April 2013 13:35, ESWAR RAO wrote:
> Hi All,
>
> I observed that automatic failover behaviour is not working with my nginx
> server.
What you describe is exactly what I would expect. No HTTP-compliant
proxy would shunt an active connection, mid-request, over to another
backend once a TCP con
Can anyone provide me some insight on this issue.
--
Posted via http://www.ruby-forum.com/.
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
15 matches
Mail list logo