The last request before this 502 request is almost 20 minutes ago and its
response code is 200.
The proxy_next_upstream conf:
proxy_next_upstream error timeout invalid_header http_502 http_503 http_504;
Here is the access log. The upstream server 192.168.0.6 is DOWN. The line-10 is
the 502
There's "can you?" and there's "should you?" My attitude is that life is short,
so I want to avoid building any opportunities to break.
Imagine that you deploy your N web apps. There can be a real value in being
able to access the web app directly when debugging, and avoiding the web server
lay
Hello!
On Thu, May 11, 2017 at 10:32:41PM +0800, Muhui Jiang wrote:
> Recently, I did an experiment to test the memory consumption of nginx. I
> request a large static zip file. I explored the debug information of nginx.
>
> For H2, below is a part of the log, I noticed that every time server wi
Hi
Recently, I did an experiment to test the memory consumption of nginx. I
request a large static zip file. I explored the debug information of nginx.
For H2, below is a part of the log, I noticed that every time server will
allocate 65536 bytes, I increase the connection number, I noticed that
Hello,
I built nginx with ngx_http_auth_pam_module, setup linux-pam for local
passwords with pam_unix module and setup nginx to use this pam config.
Linux-pam config file is below:
authsufficient pam_unix.so nullok
account required pam_unix.so
When I did this, loading of page is ve
Hi,
On Thu, May 11, 2017 at 09:42:35AM +, Alexander Chekalin wrote:
> Thank you for the patch (and your attention). The only thing I don’t like in
> the idea is that patch is against nginx source, right? Just in a case nginx
> will ever change the source (and the patch is a bit outdated, isn
Hi Jason,
On Wed, May 10, 2017 at 09:02:36PM -0700, Jason Bronnx wrote:
> Hi,
>
> Tried to search on this for a couple of hours, but had no luck, hoping you
> guys can help.
>
> I have a use case, that I need to proxy the request to server-A first, then
> if returns 200, then it'll query server-
Thank you for the patch (and your attention). The only thing I don’t like in
the idea is that patch is against nginx source, right? Just in a case nginx
will ever change the source (and the patch is a bit outdated, isn’t it?) we can
see problems on patching newer versions.
Just out of curiosity
