You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Arnaud Grandville <ag...@gmail.com> on 2018/03/25 16:40:46 UTC
Client closed request
Hi the list,
I’m using httpd as reverse proxy to rewrite and forward URL to numerous
targets servers.
Under heavy load conditions, some requests are not served whereas no errors
are found on access logs.
After investigations, I understand that some clients closed connection
before the response is sent.
I worked on a patch to return a specific http error code in such situation.
The new http 499 code in access log
127.0.0.1 - - [25/Mar/2018:17:32:12 +0200] "GET /aa HTTP/1.1" 200 564
127.0.0.1 - - [25/Mar/2018:17:33:07 +0200] "GET /aa HTTP/1.1" 499 564
127.0.0.1 - - [25/Mar/2018:17:40:52 +0200] "GET / HTTP/1.1" 404 198
127.0.0.1 - - [25/Mar/2018:17:41:10 +0200] "GET / HTTP/1.1" 499 198
Let me know what you think about it.
Arnaud
Re: Client closed request
Posted by Eric Covener <co...@gmail.com>.
On Sun, Mar 25, 2018 at 12:40 PM, Arnaud Grandville
<ag...@gmail.com> wrote:
> Hi the list,
>
> I’m using httpd as reverse proxy to rewrite and forward URL to numerous
> targets servers.
>
> Under heavy load conditions, some requests are not served whereas no errors
> are found on access logs.
>
> After investigations, I understand that some clients closed connection
> before the response is sent.
>
> I worked on a patch to return a specific http error code in such situation.
>
> The new http 499 code in access log
>
> 127.0.0.1 - - [25/Mar/2018:17:32:12 +0200] "GET /aa HTTP/1.1" 200 564
>
> 127.0.0.1 - - [25/Mar/2018:17:33:07 +0200] "GET /aa HTTP/1.1" 499 564
>
> 127.0.0.1 - - [25/Mar/2018:17:40:52 +0200] "GET / HTTP/1.1" 404 198
>
> 127.0.0.1 - - [25/Mar/2018:17:41:10 +0200] "GET / HTTP/1.1" 499 198
>
IIUC %X is normally used to log this condition.