when client->server socket is closed also server->client is closed and request is aborted ?
jarkko.torppa at elisa.fi
Tue Oct 31 14:25:48 UTC 2017
Indeed that was it (uwsgi_ignore_client_abort on) I kinda feel that this should be on by default for http/1.0 and connection: close clients.
The client that I had trouble with was org.apache.xmlrpc.client java class
From: nginx [mailto:nginx-bounces at nginx.org] On Behalf Of Richard Stanway via nginx
Sent: 26. lokakuuta 2017 16:33
To: nginx at nginx.org
Cc: Richard Stanway <r1ch+nginx at teamliquid.net>
Subject: Re: when client->server socket is closed also server->client is closed and request is aborted ?
Look at http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_ignore_client_abort or http://nginx.org/en/docs/http/ngx_http_fastcgi_module.html#fastcgi_ignore_client_abort etc depending on what you're doing with the request.
On Thu, Oct 26, 2017 at 1:07 PM, Torppa Jarkko <jarkko.torppa at elisa.fi<mailto:jarkko.torppa at elisa.fi>> wrote:
I have an old xmlrpc client that seems to close the client->server side of the socket immediately after it has sent the request to server, server seems to close the server->client side of socket in response to this.
I have been trying to find setting for this, cannot find one.
Also have been trying do dig into the sources to see where this happens, but no luck so far.
nginx mailing list
nginx at nginx.org<mailto:nginx at nginx.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nginx