Welcome to the Second Life Forums Archive

These forums are CLOSED. Please visit the new forums HERE

llHttpRequest returns error 499
Stone Juran
Registered User
Join date: 21 Mar 2007
Posts: 28
03-25-2008 02:13
Hello,

I used to have a website hosted at free.fr working with LSL scripts, all was ok, no problems at all.

Now I have set up a website at home, and it works with any browser, from outside connections, some friends could access from their home. Now, when I try to access it with a LSL script, i have an error 499. But the same request works on other browser from anywhere.

I use Apache 2. When I look at the apache logs, I see SL requests (HTTP 1.0) and other requests (HTTP 1.1). The http requests for SL hav a HTTP code 200, so it seems normal from the web server side. But SL keeps on sending 499 errors.

Do you have any idea of what it can be, and how to correct this? I have full access on the web server and can correct any parameter.

Thank you very much

Stone
Salvador Nakamura
http://www.sl-index.com
Join date: 16 Jan 2007
Posts: 557
03-25-2008 02:48
could it be that sl tries to access a closed port ?

-try switching off your firewall to see if it helps ?
Day Oh
Registered User
Join date: 3 Feb 2007
Posts: 1,257
03-25-2008 02:52
What's the contents of the response body?
Had a thing the other day where SL wouldn't let me have the response because of the content type
_____________________
Dominique Laville
Registered User
Join date: 24 Apr 2008
Posts: 84
05-17-2008 02:29
Did you solved this problem ?
I also have http error 499 after 30 seconds..
Day Oh
Registered User
Join date: 3 Feb 2007
Posts: 1,257
05-17-2008 02:41
Ok info appears!

From: http://wiki.secondlife.com/wiki/Http_response

Besides the usual HTTP status codes, SL implements a special status code 499, which can indicates:

* Request timeout (60 seconds)
* SSL failure
* A space was present in the url (escape your URL with llEscapeURL).


From: http://lslwiki.net/lslwiki/wakka.php?wakka=http_response

499 seems to indicate a failure to establish a TCP connection while 0 likely means that the connection was established but the HTTP reply was invalid. 499 can also indicate that the target has an invalid SSL certificate and you turned verification on, and also you receive a 499 when no response is received after a certain time, which currently seems to be set to 60 seconds.
_____________________
Hewee Zetkin
Registered User
Join date: 20 Jul 2006
Posts: 2,702
05-17-2008 10:25
From: Salvador Nakamura
could it be that sl tries to access a closed port ?

If the requests appear in the Apache log, PROBABLY it isn't a problem with the port. However, I wouldn't use the protocol version alone to decide whether it is a request from SL. Look at the originating IP address and see if it is in one of LL's IP address ranges: http://wiki.secondlife.com/wiki/Simulator_IP_Addresses