499 errors

We have a Rails app with nginx proxying requests to 2 mongrel servers.
I’m seeing a lot of 499 errors crop up, for example:

lodgeit.aioi.local-access.log-20100603:192.168.0.50 - -
[02/Jun/2010:09:32:39 +1000] “GET /?page=61 HTTP/1.1” 499 0
http://lodgeit/?page=57” “Mozilla/5.0 (Windows; U; Windows NT 5.2;
en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729)”
lodgeit.aioi.local-access.log-20100603:192.168.0.50 - -
[02/Jun/2010:09:32:39 +1000] “GET /?page=61 HTTP/1.1” 499 0
http://lodgeit/?page=57” “Mozilla/5.0 (Windows; U; Windows NT 5.2;
en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729)”
lodgeit.aioi.local-access.log-20100603:192.168.0.50 - -
[02/Jun/2010:09:32:39 +1000] “GET /?page=61 HTTP/1.1” 499 0
http://lodgeit/?page=57” “Mozilla/5.0 (Windows; U; Windows NT 5.2;
en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729)”
lodgeit.aioi.local-access.log-20100603:192.168.0.50 - -
[02/Jun/2010:09:32:40 +1000] “GET /?page=61 HTTP/1.1” 499 0
http://lodgeit/?page=57” “Mozilla/5.0 (Windows; U; Windows NT 5.2;
en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729)”
lodgeit.aioi.local-access.log-20100603:192.168.0.50 - -
[02/Jun/2010:09:32:40 +1000] “GET /?page=61 HTTP/1.1” 499 0
http://lodgeit/?page=57” “Mozilla/5.0 (Windows; U; Windows NT 5.2;
en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729)”
lodgeit.aioi.local-access.log-20100603:192.168.0.50 - -
[02/Jun/2010:09:32:40 +1000] “GET /?page=61 HTTP/1.1” 499 0
http://lodgeit/?page=57” “Mozilla/5.0 (Windows; U; Windows NT 5.2;
en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729)”
lodgeit.aioi.local-access.log-20100603:192.168.0.50 - -
[02/Jun/2010:09:32:40 +1000] “GET /?page=61 HTTP/1.1” 499 0
http://lodgeit/?page=57” “Mozilla/5.0 (Windows; U; Windows NT 5.2;
en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729)”
lodgeit.aioi.local-access.log-20100603-192.168.0.50 - -
[02/Jun/2010:09:32:42 +1000] “GET /?page=61 HTTP/1.1” 200 13763
http://lodgeit/?page=57” “Mozilla/5.0 (Windows; U; Windows NT 5.2;
en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729)”

I understand the 499 error is because of the client closing the
connection before nginx can send the response. I hope someone more
technical than me can explain what might be causing 7 GETs in the space
of one second. Users are using Firefox. I wonder if Firefox might be
causing this behaviour?

Thanks in advance
Nick

192.168.0.50 is a reverse proxy?

On Thu, Jun 17, 2010 at 1:42 PM, Nick T. [email protected] wrote:

We have a Rails app with nginx proxying requests to 2 mongrel servers. I’m seeing a lot of 499 errors crop up, for example:

lodgeit.aioi.local-access.log-20100603:192.168.0.50 - - [02/Jun/2010:09:32:39 +1000] “GET /?page=61 HTTP/1.1” 499 0 “http://lodgeit/?page=57” “Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729)”
I understand the 499 error is because of the client closing the connection before nginx can send the response. I hope someone more technical than me can explain what might be causing 7 GETs in the space of one second. Users are using Firefox. I wonder if Firefox might be causing this behaviour?


Ren Xiaolei

192.168.0.50 is a terminal server.


Nick T.

Analyst/Programmer
Aioi Insurance Co., Ltd
T: +61 3 9869 0125
E: [email protected]mailto:[email protected]

On 17/06/2010, at 8:22 PM, 任晓磊 wrote:

192.168.0.50


This email is intended for the use of the individual or entity it is
addressed to and may contain information that is confidential, legally
privileged, commercially sensitive, or protected by copyright. If it
contains financial product advice, the advice is of a general nature and
you will need to determine how appropriate it is for you.

If you are not the intended recipient you must not disclose,
disseminate, distribute or copy information contained in it. If you have
received this e-mail in error, please notify the sender immediately and
destroy the original message. While this mail and any attachments have
been scanned for common computer viruses and found to be virus free, we
recommend that you perform your own virus checks before opening any
attachments.


This email has been scrubbed for your protection by SMX.
For more information visit http://smxemail.com

I can’t understand. What’s terminal server? like Windows Terminal
Service?

On Fri, Jun 18, 2010 at 5:51 AM, Nick T. [email protected] wrote:

192.168.0.50 is a terminal server.


Ren Xiaolei

Maybe some user is trying a automatic script to refresh that URL?

On Fri, Jun 18, 2010 at 12:31 PM, Nick T. [email protected] wrote:

Yes, sorry, exactly that… 192.168.0.50 is the IP address of the machine
from which most users connect to the web application.


Ren Xiaolei

Yes, sorry, exactly that… 192.168.0.50 is the IP address of the
machine from which most users connect to the web application.


Nick T.

Analyst/Programmer
Aioi Insurance Co., Ltd
T: +61 3 9869 0125
E: [email protected]mailto:[email protected]

On 18/06/2010, at 1:45 PM, 任晓磊 wrote:

I can’t understand. What’s terminal server? like Windows Terminal
Service?

On Fri, Jun 18, 2010 at 5:51 AM, Nick T.
<[email protected]mailto:[email protected]> wrote:
192.168.0.50 is a terminal server.


Ren Xiaolei


nginx mailing list
[email protected]mailto:[email protected]
http://nginx.org/mailman/listinfo/nginx


This email is intended for the use of the individual or entity it is
addressed to and may contain information that is confidential, legally
privileged, commercially sensitive, or protected by copyright. If it
contains financial product advice, the advice is of a general nature and
you will need to determine how appropriate it is for you.

If you are not the intended recipient you must not disclose,
disseminate, distribute or copy information contained in it. If you have
received this e-mail in error, please notify the sender immediately and
destroy the original message. While this mail and any attachments have
been scanned for common computer viruses and found to be virus free, we
recommend that you perform your own virus checks before opening any
attachments.


This email has been scrubbed for your protection by SMX.
For more information visit http://smxemail.com