Hi!
I'm using Nginx as a proxy to Apache.
I noticed some messages in my error.log that I cannot explain:
27463#0: *125209 no live upstreams while connecting to upstream, client:
x.x.x.x, server: www.xxx.com, request: "GET /xxx/ HTTP/1.1", upstream: "
http://backend/xxx/";, host: "www.xxx.com"
Th
s it’s first location ‘/‘ from where
> you route to other 2 locations.
>
> also, try to log in debug mode, may be that will give more insights.
>
> br,
> Aziz.
>
>
>
>
>
> > On 13 Nov 2017, at 21:47, Jean-Paul Hemelaar
> wrote:
> >
> > Hi,
>
CC_2“not-so-strict";
> # .. more country codes;
> }
>
> # strict and not-so-strict locations
>
> map $strictness $path {
>"strict” "/strict/";
>"not-so-strict” "/not-so-strict/“;
> }
>
> location / {
>retu
gt;
>
>
> br,
> Aziz.
>
>
>
>
>
> > On 12 Nov 2017, at 14:03, Jean-Paul Hemelaar
> wrote:
> >
> > Hi!
> >
> > I'm using Nginx together with Naxsi; so not sure it this is the correct
> place for this post, but I'll give it a try.
>
Hi!
I'm using Nginx together with Naxsi; so not sure it this is the correct
place for this post, but I'll give it a try.
I want to configure two detection thresholds: a strict detection threshold
for 'far away countries', and a less-strict set
for local countries. I'm using a setup like:
locatio
I think this solves the issue: http://hg.nginx.org/nginx/rev/9552758a786e
Thanks,
JP
On Wed, Mar 15, 2017 at 11:05 AM, Jean-Paul Hemelaar
wrote:
> Hi,
>
> I noticed a delay of approx. 200ms when the proxy_cache_background_update
> is used and Nginx sends stale content t
Hi,
I have a similar issue:
http://mailman.nginx.org/pipermail/nginx/2017-March/053198.html
I noticed (using tcpdump) that all data except the last package is send
immediately.
Can you verify it that's happening in your case as well?
JP
On Wed, Apr 5, 2017 at 1:32 PM, IgorR wrote:
> Hello,
>
Hi,
I noticed a delay of approx. 200ms when the proxy_cache_background_update
is used and Nginx sends stale content to the client.
Current setup:
- Apache webserver as backend sending a slow response delay.php that simply
waits for 1 second:
- Nginx in front to cache the response, and send stale
fetch it
properly
As a workaround I included "rewrite ^/index.html$ / break;" to rewrite the
/index.html call to a simple / for the backend server.
This works, but is not ideal.
Is there a better way to tell Nginx to just fetch "/"?
Thanks,
