Skip to content
lsl.devlsl.devLSL Dev

Category:LSL HTTP

This is a historical wiki category. Explore the current topic guides →

LSL Header: {{LSL Header|ml=*}}

HTTP

LSL includes functions that utilize HTTP, the HyperText Transfer Protocol, for communicating with other scripts in-world or web servers on the outside internet. HTTP requests incur no speed penalty, but there is a limit on how many requests per object can be made.

Functions

;llEscapeURL: Returns the UTF-8 encoded escape codes for selected characters.
;llHTTPRequest: Requests information from an HTTP server.
;llLoadURL: Loads a web page in an external browser.
;llUnescapeURL: Returns the UTF-8 characters without escape codes.
;llHTTPResponse: Responds to an HTTP request made to the script.
;llGetFreeURLs: Returns the number of URLs that the script can request for HTTP-In.
;llGetHTTPHeader: Returns the value of the requested header for a given HTTP request made to the script.
;llReleaseURL: Releases a given URL so it may not be used further.
;llRequestURL: Requests a non-secure URL to be used with HTTP-In.
;llRequestSecureURL: Same as llRequestURL but requests a secure url (https://)
;llSetContentType: sets the content type for non-text http responses. Called in the http_request event before the call to the function llHTTPResponse . ( or inside user-defined functions called in the http_request event )

Events

;http_request: Called when the script receives an HTTP request.
;http_response: Called when an HTTP request is complete.

Understanding LSL HTTP Communications

Original wiki source

Some wiki templates and tables need their original context. View this article on the Second Life Wiki. Technical wording and examples are retained from the source; historical guidance may differ from current behavior.

From the Second Life Wiki

Community documentation adapted from Category:LSL HTTP, by Linden Research, Inc. and contributing residents.View contributors and history.

Imported wiki revision:

Licensed under CC BY-SA 3.0. Last wiki edit: .Formatting and links have been adapted for this site; API metadata follows the LSL definitions.