Http response
| LSL Portal | Functions | Events | Types | Operators | Constants | Flow Control | Script Library | Categorized Library | Tutorials |
Description
Event: http_response( key request_id, integer status, list metadata, string body ){ ; }| 32 | Event ID |
Triggered when task receives a response to one of its llHTTPRequests
| • key | request_id | – | Matches return from llHTTPRequest | |
| • integer | status | – | HTTP code (like 404 or 200) | |
| • list | metadata | – | List of HTTP_* constants and attributes | |
| • string | body |
Specification
Status 415 "Unsupported or unknown Content-Type"
The remote server did reply to your request but the Content-Type of the reply (such as XML, JSON, Atom, RSS, PLS) is not recognized by the LL server and so is not passed back to the script. You can assume that 415 means the server heard your request and did reply.
Status 499
Besides the usual HTTP status codes, SL implements a special status code 499. This code isn't generated by the remote web server but by SL's servers, it can indicate:
- Request timeout (60 seconds)
- SSL failure
- A space was present in the url (escape your URL with llEscapeURL).
Status 502
The proxy server received an invalid response from an upstream server. This error occurs when you send an llHTTPRequest to an object in-world, and it does not reply with an llHTTPResponse.
| Constant | Type | Description | |
|---|---|---|---|
| HTTP_BODY_TRUNCATED | 0 | integer | Truncation point in bytes |
Caveats
- This events will be triggered in every script in the prim, not just in the requesting script.
- It is not guaranteed that there will be an http_response for every llHTTPRequest().
- If the script moves to a different region before the remote HTTP server can respond, the response will be lost. [1]
Examples
<lsl>key http_request_id;
default {
state_entry()
{
http_request_id = llHTTPRequest("url", [], "");
}
http_response(key request_id, integer status, list metadata, string body)
{
if (request_id == http_request_id)
{
llSetText(body, <0,0,1>, 1);
}
}
}</lsl>
To parse POST content: <lsl> string get_post_value(string content, string returns){
//This parses application/x-www-form-urlencoded POST data
//For instance if the webserver posts 'data1=hi&data2=blah' then
//calling get_post_value("data1=hi&data2=blah","data1"); would return "hi"
//Written by MichaelRyan Allen, Unrevoked Clarity
list p = llParseString2List(content,["&"],[]);
integer n = llGetListLength(p);
integer i;
list names;
list values;
for(i=0;i!=n;i++){
list p2 = llParseString2List(llList2String(p,i),["="],[]);
names += llUnescapeURL(llList2String(p2,0));
values += llUnescapeURL(llList2String(p2,1));
}
if(llListFindList(names,(list)returns) == -1){
return "";
}
else{
return llList2String(values,llListFindList(names,(list)returns));
}
}
</lsl>
Notes
Parsing Problems
If for some reason while using llHTTPRequest/http_response you are unable to parse a known good RSS feed or some other form of web contents, you will need to work around it outside of SecondLife. This is unlikely to change in the near future since checking the headers requires more overhead at the simulator level.
Unicode
When serving content with UTF-8 characters be sure your server sets the outgoing "Content-Type" header so that it includes "charset=utf-8" otherwise it will be interpreted incorrectly. See W3C:Setting the HTTP charset parameter for further details.
Request Headers
| Header | Description | Example data |
|---|---|---|
| Connection | Connection options | close |
| Cache-Control | Maximum response age accepted. | max-age=259200 |
| X-Forwarded-For | Used to show the IP address connected to through proxies. | 127.0.0.1 |
| Via | Shows the recipients and protocols used between the User Agent and the server. | 1.1 sim10115.agni.lindenlab.com:3128 (squid/2.7.STABLE9) |
| Content-Length | The size of the entity-body, in decimal number of octets. | 17 |
| Pragma | The message should be forwarded to the server, even if it has a cached version of the data. | no-cache |
| X-SecondLife-Shard | The environment the object is in. "Production" is the main grid and "Testing" is the preview grid | Production |
| X-SecondLife-Region | The name of the region the object is in, along with the global coordinates of the region's south-west corner | Jin Ho (264448, 233984) |
| X-SecondLife-Owner-Name | Legacy name of the owner of the object | Zeb Wyler |
| X-SecondLife-Owner-Key | UUID of the owner of the object | 01234567-89ab-cdef-0123-456789abcdef |
| X-SecondLife-Object-Name | The name of the object containing the script | Object |
| X-SecondLife-Object-Key | The key of the object containing the script | 01234567-89ab-cdef-0123-456789abcdef |
| X-SecondLife-Local-Velocity | The velocity of the object | 0.000000, 0.000000, 0.000000 |
| X-SecondLife-Local-Rotation | The rotation of the object containing the script | 0.000000, 0.000000, 0.000000, 1.000000 |
| X-SecondLife-Local-Position | The position of the object within the region | (173.009827, 75.551231, 60.950001) |
| User-Agent | The user-agent header sent by LSL Scripts. Contains Server version. | Second Life LSL/16.05.24.315768 (http://secondlife.com) |
| Content-Type | The media type of the entity body. | text/plain; charset=utf-8 |
| Accept-Charset | Acceptable character sets from the server. Q being the quality expected when sending the different character sets. | utf-8;q=1.0, *;q=0.5 |
| Accept | Media types the server will accept. | text/*, application/xhtml+xml, application/atom+xml, application/json, application/xml, application/llsd+xml, application/x-javascript, application/javascript, application/x-www-form-urlencoded, application/rss+xml |
| Accept-Encoding | Acceptable content encodings for the server. | deflate, gzip |
| Host | The internet host being requested. | secondlife.com |
|
||
See Also
Functions
| • | llHTTPRequest |
Deep Notes
Signature |
|---|
event void http_response( key request_id, integer status, list metadata, string body ); |