Difference between revisions of "Template:LSL Constants HTTP"

From Second Life Wiki
Jump to navigation Jump to search
m
Line 1: Line 1:
{{{!}} class="sortable" {{Prettytable|style=margin-top:0;}}
{{#if:
 
{{LSL Function/boolean|verify|if=*|td=the server SSL certificate must be verifiable using one of the standard certificate authorities|fd=any server SSL certificate will be accepted.}}
 
{{LSL Function/boolean|noisy|if=*|td=shout error messages to DEBUG_CHANNEL if the outgoing request rate exceeds the server limit|fd=the error messages are suppressed.}}
 
{{#vardefine:p_method_hover|A valid HTTP method, such as {{String|GET}}, {{String|POST}}, {{String|PUT}} and {{String|DELETE}}}}
 
{{#vardefine:p_name_hover|The name of the header to be set.}}
{{#vardefine:p_value_hover|The value of the header to be set.}}
 
{{#vardefine:p_length_hover|The maximum length allowed for an HTTP body, this is also capped by the VM in use.}}
 
{{#vardefine:p_MIME_type_hover|}}
 
}}{{{!}} class="sortable" {{Prettytable|style=margin-top:0;}}
{{!}}-{{Hl2}}
{{!}}-{{Hl2}}
! '''Flag'''
! '''Flag'''
Line 15: Line 30:
{{!}} {{LSL Const|HTTP_MIMETYPE|integer|1}}
{{!}} {{LSL Const|HTTP_MIMETYPE|integer|1}}
{{!}} {{#var:value}}
{{!}} {{#var:value}}
{{!}} <nowiki>[</nowiki>[[string]]&nbsp;{{LSL Param|MIMEtype}}<nowiki>]</nowiki>
{{!}} <nowiki>[</nowiki>[[string]]&nbsp;{{LSL Param|MIME_type}}<nowiki>]</nowiki>
{{!}} <nowiki>[</nowiki>"text/plain;charset=utf-8"<nowiki>]</nowiki>
{{!}} <nowiki>[</nowiki>"text/plain;charset=utf-8"<nowiki>]</nowiki>
{{!}} text/* MIME types should specify a charset. To emulate HTML forms use application/x-www-form-urlencoded. This allows you to set the body to a properly escaped ([[llEscapeURL]]) sequence of &lt;name,value&gt; pairs in the form var=value&amp;var2=value2 and have them automatically parsed by web frameworks
{{!}} text/* MIME types should specify a charset. To emulate HTML forms use application/x-www-form-urlencoded. This allows you to set the body to a properly escaped ([[llEscapeURL]]) sequence of &lt;name,value&gt; pairs in the form var=value&amp;var2=value2 and have them automatically parsed by web frameworks
Line 29: Line 44:
{{!}} {{LSL Const|HTTP_VERIFY_CERT|integer|3}}
{{!}} {{LSL Const|HTTP_VERIFY_CERT|integer|3}}
{{!}} {{#var:value}}
{{!}} {{#var:value}}
{{!}} <nowiki>[</nowiki>[[integer]]&nbsp;{{HoverText|boolean|TRUE or FALSE}}<nowiki>]</nowiki>
{{!}} <nowiki>[</nowiki>[[integer]]&nbsp;{{LSL Param|verify}}<nowiki>]</nowiki>
{{!}} <nowiki>[</nowiki>[[TRUE]]<nowiki>]</nowiki>
{{!}} <nowiki>[</nowiki>[[TRUE]]<nowiki>]</nowiki>
{{!}} If [[TRUE]], the server SSL certificate must be verifiable using one of the standard certificate authorities when making HTTPS requests. If [[FALSE]], any server SSL certificate will be accepted.
{{!}} If [[TRUE]], the server SSL certificate must be verifiable using one of the standard certificate authorities when making HTTPS requests. If [[FALSE]], any server SSL certificate will be accepted.
Line 35: Line 50:
{{!}} {{LSL Const|HTTP_VERBOSE_THROTTLE|integer|4}}
{{!}} {{LSL Const|HTTP_VERBOSE_THROTTLE|integer|4}}
{{!}} {{#var:value}}
{{!}} {{#var:value}}
{{!}} <nowiki>[</nowiki>[[integer]]&nbsp;{{LSL Param|verbosity}}<nowiki>]</nowiki>
{{!}} <nowiki>[</nowiki>[[integer]]&nbsp;{{LSL Param|noisy}}<nowiki>]</nowiki>
{{!}} <nowiki>[</nowiki>[[TRUE]]<nowiki>]</nowiki>
{{!}} <nowiki>[</nowiki>[[TRUE]]<nowiki>]</nowiki>
{{!}} If [[TRUE]], shout error messages to [[DEBUG_CHANNEL]] if the outgoing request rate exceeds the server limit. If [[FALSE]], the error messages are suppressed (llHTTPRequest will still return [[NULL_KEY]]).
{{!}} If [[TRUE]], shout error messages to [[DEBUG_CHANNEL]] if the outgoing request rate exceeds the server limit. If [[FALSE]], the error messages are suppressed (llHTTPRequest will still return [[NULL_KEY]]).
Line 42: Line 57:
{{!}} {{#var:value}}
{{!}} {{#var:value}}
{{!}} <nowiki>[</nowiki>[[string]]&nbsp;{{LSL Param|name}}, [[string]]&nbsp;{{LSL Param|value}}<nowiki>]</nowiki>
{{!}} <nowiki>[</nowiki>[[string]]&nbsp;{{LSL Param|name}}, [[string]]&nbsp;{{LSL Param|value}}<nowiki>]</nowiki>
{{!}} No implied default values.
{{!}} NA
{{!}} Add an extra custom HTTP header to the request.  The first string is the {{LSL Param|name}} of the parameter to change, e.g. "Pragma", and the second string is the {{LSL Param|value}}, e.g. "no-cache".  Up to 8 custom headers may be configured per request.  Note that certain headers, such as the default headers, are blocked for security reasons.
{{!}} Add an extra custom HTTP header to the request.  The first string is the name of the parameter to change, e.g. "Pragma", and the second string is the value, e.g. "no-cache".  Up to 8 custom headers may be configured per request.  Note that certain headers, such as the default headers, are blocked for security reasons.
{{!}}}
{{!}}}

Revision as of 15:02, 22 October 2012

Flag Parameter(s) Default Parameter Value(s) Description
HTTP_METHOD 0 [string method] ["GET"] "GET", "POST", "PUT" and "DELETE"
HTTP_MIMETYPE 1 [string MIME_type] ["text/plain;charset=utf-8"] text/* MIME types should specify a charset. To emulate HTML forms use application/x-www-form-urlencoded. This allows you to set the body to a properly escaped (llEscapeURL) sequence of <name,value> pairs in the form var=value&var2=value2 and have them automatically parsed by web frameworks
HTTP_BODY_MAXLENGTH 2 [integer length] [2048] Sets the maximum (UTF-8 encoded) byte length of the HTTP body. The maximum that can be set depends upon which VM is used.
HTTP_VERIFY_CERT 3 [integer verify] [TRUE] If TRUE, the server SSL certificate must be verifiable using one of the standard certificate authorities when making HTTPS requests. If FALSE, any server SSL certificate will be accepted.
HTTP_VERBOSE_THROTTLE 4 [integer noisy] [TRUE] If TRUE, shout error messages to DEBUG_CHANNEL if the outgoing request rate exceeds the server limit. If FALSE, the error messages are suppressed (llHTTPRequest will still return NULL_KEY).
HTTP_CUSTOM_HEADER 5 [string name, string value] NA Add an extra custom HTTP header to the request. The first string is the name of the parameter to change, e.g. "Pragma", and the second string is the value, e.g. "no-cache". Up to 8 custom headers may be configured per request. Note that certain headers, such as the default headers, are blocked for security reasons.