Welcome! Log In Create A New Profile

Advanced

Re: 400 bad request errors

October 06, 2009 01:08PM
>>It may be browser that has started an images
>>download and has stopped the connection, because user has clicked on a link.

I thought that in this case, the response was HTTP 499 [ NGINX_HTTP_CLIENT_CLOSED_REQUEST ]

with this in the configuration file, the behavior would be the same?

server {
server_name "";
return 444;
}

thanks.
Subject Author Posted

400 bad request errors

pepejose September 28, 2009 10:07AM

Re: 400 bad request errors

Maxim Dounin September 28, 2009 10:30AM

Re: 400 bad request errors

Ray September 28, 2009 10:40AM

Re: 400 bad request errors

pepejose September 28, 2009 10:44AM

Re: 400 bad request errors

Maxim Dounin September 28, 2009 10:56AM

Re: 400 bad request errors

pepejose September 28, 2009 11:02AM

Re: 400 bad request errors

pepejose October 01, 2009 04:13AM

Re: 400 bad request errors

pepejose October 06, 2009 10:19AM

Re: 400 bad request errors

Igor Sysoev October 06, 2009 10:44AM

Re: 400 bad request errors

pepejose October 06, 2009 10:56AM

Re: 400 bad request errors

pepejose October 06, 2009 11:12AM

Re: 400 bad request errors

Igor Sysoev October 06, 2009 11:20AM

Re: 400 bad request errors

pepejose October 06, 2009 11:53AM

Re: 400 bad request errors

Igor Sysoev October 06, 2009 12:50PM

Re: 400 bad request errors

pepejose October 06, 2009 01:08PM

Re: 400 bad request errors

pepejose October 07, 2009 10:57AM

Re: 400 bad request errors

Igor Sysoev October 07, 2009 11:20AM

Re: 400 bad request errors

cdan18po October 08, 2009 02:35AM

Re: 400 bad request errors

pepejose October 08, 2009 09:59AM

Re: 400 bad request errors

Igor Sysoev October 08, 2009 10:26AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 68
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready