Hi to all,
I have a NGINX and configure it as load balancer (hash remote_IP) in front
of java application. When number of requests are normal all things good and
working fine but when requests go high NGINX has a delay to response to
each request. at this moment if I stop NGINX and requests
> Subject: Can someone explain me why "curl: (7) Failed to connect to
> 127.0.0.1 port 2000: Connection refused" ?
>
> Hi!,
>
> I do not understand why it says "curl: (7) Failed to connect to 127.0.0.1 port
> 2000: Connection refused" :
> curl -X POST -F 'first_name=pinco' -F 'last_name=pallo'
Hi!,
I do not understand why it says "curl: (7) Failed to connect to 127.0.0.1
port 2000: Connection refused" :
curl -X POST -F 'first_name=pinco' -F 'last_name=pallo' -F
'company_name=Company' -F 'email=pinco.pa...@company.com' -F 'tel=1'
127.0.0.1:2000/puser/add curl: (7) Failed to
I solved it .
It was mix of small little problems that together hindered the correct
answer:
- changed in golang webserver HOST = 127.0.0.1
- capitalized the first letter of each element of the Puser struct in order
to make it visible to json decoder
- used correctly the curl command:
curl
Hello!
On Wed, May 13, 2020 at 10:17:18PM +0800, Jim T wrote:
> In ngx_http_upstream_test_next, the loop will continue when the status is
> matched, and the ngx_http_upstream_next_errors is non-repeating. I think we
> can jump out of for the unnecessary loop, and here is my patch:
>
> # HG
Hello!
On Mon, May 04, 2020 at 02:14:26AM +0200, Krzysztof Grzadziel wrote:
> # HG changeset patch
> # User Krzysztof Grządziel
> # Date 1588474577 -7200
> # Sun May 03 04:56:17 2020 +0200
> # Node ID ae1a050faa5c718dc81928dced93337f1e64a4e6
> # Parent
details: https://hg.nginx.org/nginx/rev/3c8082c3f98a
branches:
changeset: 7649:3c8082c3f98a
user: Jinhua Tan <312841...@qq.com>
date: Wed May 13 22:02:47 2020 +0800
description:
Upstream: jump out of loop after matching the status code.
diffstat:
src/http/ngx_http_upstream.c | 2
Hi:
In ngx_http_upstream_test_next, the loop will continue when the status is
matched, and the ngx_http_upstream_next_errors is non-repeating. I think we
can jump out of for the unnecessary loop, and here is my patch:
# HG changeset patch
# User Jinhua Tan <312841...@qq.com>
# Date 1589378567
