Difference between revisions of "LlHTTPResponse"

From Second Life Wiki
Jump to navigation Jump to search
m (changed example script to Void's version)
m (arg)
Line 60: Line 60:
         {
         {
             llOwnerSay("Something went wrong, no URL.\n" + body);
             llOwnerSay("Something went wrong, no URL.\n" + body);
        }
        else
        {
            llOwnerSay("Ummm... I have no idea what SL just did. Method=\""+method+"\"\n" + body);
         }
         }
     }
     }

Revision as of 13:23, 22 October 2012

Summary

Function: llHTTPResponse( key request_id, integer status, string body );
0.0 Forced Delay
10.0 Energy

Responds to request_id with status and body.

• key request_id A valid HTTP request key.
• integer status HTTP Status (200, 400, 404, etc)
• string body Contents of the response.

The response need not be made inside the http_request event but if it does not happen in a timely fashion the request will time out (within 25 seconds).

Caveats

  • This call must be made by the script containing the http_request event where the request_id was received.
  • There is no limit, other than script size, to the amount of data that can be sent by this function.
    • llHTTPRequest can truncate the response length in receiving scripts. Be aware when using them together for prim-to-prim communications.
  • Returns 'content-type: text/plain' by default. Use llSetContentType to optionally return 'text/html' if being viewed by the object owner within a Second Life client.

Examples

<lsl> string url;

default {

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

See Also

Events

•  http_request

Functions

•  llGetFreeURLs
•  llRequestURL
•  llRequestSecureURL
•  llReleaseURL
•  llGetHTTPHeader
•  llSetContentType

Articles

•  LSL http server

Deep Notes

History

Signature

function void llHTTPResponse( key request_id, integer status, string body );