Re: Error 499 (Hi again, Kelly!)

Well, this is odd.

See, whenever my scripts get an error 499 returned from an HTTP request to my home or rented virtual server, the request that generated it does not show up in my logs on my web server. (Apache 2.0.58 for my home) This would be why I was asking, as not only does Apache not have a 499, it's not even getting the request to generate an error in the first place.

Are you sure it's not the proxy returning a "woah, too busy!" error of some sort? Or (as someone guessed in the LSL wiki) some inability to open the socket in the first place?

I get this error from all sorts of requests, too. From requests to my home-based server, to my virtual server at secure.net, even to services like the population information set up by LL.

Even more curious, while vendors in other regions are passing requests without this error, another region's scripts will get this 499 several times in a row.

A link to my first question and Kelly's response.

SL servers definitely return their own error codes. If you request http://nonexistant you get a 503, and internal addresses like http://127.0.0.1 or http://www.secondlife.com get you a 403. 499 seems to be used for request timeouts and possibly refused connections or other miscellaneous errors. Try http://11.22.33.44 or a script that does not respond within 60 seconds, and you'll get a 499. It is the only one that is returned without a description of the error in the response body.

Ok, thank you. This is what I expected.
I've never met a proxy that didn't occasionally inject information for various reasons. It's useful to know this means what it seemed to mean, and my scripts can handle it in a more graceful manner than they currently do.