Http request

Template:Needs Translation/LSL/de Template:Needs Translation/LSL/es Template:Needs Translation/LSL/el Template:Needs Translation/LSL/he Template:Needs Translation/LSL/it Template:Needs Translation/LSL/ko Template:Needs Translation/LSL/nl Template:Needs Translation/LSL/hu Template:Needs Translation/LSL/no Template:Needs Translation/LSL/da Template:Needs Translation/LSL/sv Template:Needs Translation/LSL/tr Template:Needs Translation/LSL/pl Template:Needs Translation/LSL/pt Template:Needs Translation/LSL/ru Template:Needs Translation/LSL/th Template:Needs Translation/LSL/uk Template:Needs Translation/LSL/zh-Hans Template:Needs Translation/LSL/zh-Hant

/LSL

http_request

Description

Event: http_request( key request_id, string method, string body ){ ; }

33	Event ID
	Delay

Triggered when task receives an HTTP request.

• key	request_id	–	HTTP request id for response use, and function response identification.
• string	method	–	"GET", "POST", "PUT", "DELETE", URL_REQUEST_GRANTED, URL_REQUEST_DENIED
• string	body	–	Contents of the request.

Specification

See LSL_http_server for full specification.

Caveats

• body is limited to 2048 bytes; anything longer will be truncated to 2048 bytes.
• headers (accessed with llGetHTTPHeader) are limited to 255 bytes.
• There is a limit of 64 pending http_request
• body is not sent with the request unless the method is set to POST, PUT, or URL_REQUEST_GRANTED
• Requests made at approx 0625 SLT may fail with a 503 status code, with "ERROR: The requested URL could not be retrieved", and "(111) Connection refused" in the body of the response. This has been confirmed as expected behaviour by Kelly, due to the nightly maint & log rotation. It does reliably impact object to object HTTP at that time, and quite probably may impact object to/from web around the same time. The interruption in service is fairly brief, and the precise timing may vary as LL adjust their nightly maint processes, or due to server load.

Examples

See LSL_http_server/examples for some examples from the feature design phase.

Important: Never ever forget to release a URL again which you have requested! URLs are region resources just like prims. If you take them all you can get into big trouble with the sim owner and/or estate managers.

<lsl> string url; key urlRequestId; key selfCheckRequestId;

request_url() {

   llReleaseURL(url);
   url = "";

   urlRequestId = llRequestURL();

}

throw_exception(string inputString) {

   key owner = llGetOwner();
   llInstantMessage(owner, inputString);

   // yeah, bad way to handle exceptions by restarting.
   // However this is just a demo script...

   llResetScript();

}

default {

   on_rez(integer start_param)
   {
       llResetScript();
   }

   changed(integer change)
   {
       if (change & (CHANGED_OWNER

Notes

• When triggered by either llRequestURL or llRequestSecureURL the method will be either URL_REQUEST_GRANTED or URL_REQUEST_DENIED
  • If the method is URL_REQUEST_GRANTED The body will contain the full url, minus the trailing forward slash.

See Also

Functions

•	llRequestURL	–	Request a new LSL Server public URL
•	llRequestSecureURL	–	Request a new LSL Server public URL
•	llReleaseURL	–	Release a URL
•	llHTTPResponse	–	For replying to HTTP requests
•	llGetHTTPHeader	–	Returns the requested HTTP header's value
•	llEscapeURL
•	llUnescapeURL

Deep Notes

Issues

All Issues

~ Search JIRA for related Issues

SVC-1086

Design: LSL http_server

Signature
event void http_request( key request_id, string method, string body );