Http response - Revision history

Gwyneth Llewelyn: Replaced with

2024-02-17T18:59:27Z

Replaced <source> with <syntaxhighlight>

← Older revision		Revision as of 11:59, 17 February 2024
Line 22:		Line 22:
	*Request timeout (60 seconds)		*Request timeout (60 seconds)
	*SSL failure		*SSL failure
	*A space was present in the ~~url~~ (escape your URL with [[llEscapeURL]]).		*A space was present in the URL (escape your URL with [[llEscapeURL]]).
	<h3>Status 502</h3>		<h3>Status 502</h3>
	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]] [[llHTTPResponse#Caveats\|in time]].		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]] [[llHTTPResponse#Caveats\|in time]].
Line 31:		Line 31:
	**If the script moves to a different region before the remote HTTP server can respond, the response will be lost. [https://lists.secondlife.com/pipermail/secondlifescripters/2011-August/006309.html]		**If the script moves to a different region before the remote HTTP server can respond, the response will be lost. [https://lists.secondlife.com/pipermail/secondlifescripters/2011-August/006309.html]
	\|examples=		\|examples=
	<~~source~~ lang="lsl2">		<syntaxhighlight lang="lsl2">
	key http_request_id;		key http_request_id;

Line 49:		Line 49:
	}		}
	}		}
	</~~source~~>		</syntaxhighlight>
	To parse POST content:		To parse POST content:
	<~~source~~ lang="lsl2">		<syntaxhighlight lang="lsl2">
	string get_post_value(string content, string returns)		string get_post_value(string content, string returns)
	{		{
Line 80:		Line 80:
	return "";		return "";
	}		}
	</~~source~~>		</syntaxhighlight>
	Another Example:		Another Example:
	{{KBcaution\|Remember to release URLs that you have requested! They are region resources just like prims, and it is possible to use them all and break other scripts.}}		{{KBcaution\|Remember to release URLs that you have requested! They are region resources just like prims, and it is possible to use them all and break other scripts.}}
	<~~source~~ lang="lsl2">		<syntaxhighlight lang="lsl2">
	string url;		string url;
	key urlRequestId;		key urlRequestId;
Line 187:		Line 187:
	}		}
	}		}
	</~~source~~>		</syntaxhighlight>
	\|helpers		\|helpers
	\|also_header		\|also_header
Line 197:		Line 197:
	\|notes=		\|notes=
	===Parsing Problems===		===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.		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 Second Life. This is unlikely to change in the near future since checking the headers requires more overhead at the simulator level.

	===Unicode===		===Unicode===

Oz Linden at 20:29, 16 April 2018

2018-04-16T20:29:27Z

← Older revision		Revision as of 13:29, 16 April 2018
Line 25:		Line 25:
	<h3>Status 502</h3>		<h3>Status 502</h3>
	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]] [[llHTTPResponse#Caveats\|in time]].		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]] [[llHTTPResponse#Caveats\|in time]].
			<h3>Status 503</h3>
			This error occurs when you send an [[llHTTPRequest]] to an object in-world, but the request was throttled before it reached the object. The throttle allows many requests per second to the set of scripts in the region that have the same owner. The response returns an HTTP Retry-After header to inform the caller how soon it may be attempted, but at present there is no way to access response headers in LSL.
	\|caveats=*This events will be triggered in every script in the prim, not just in the [[llHTTPRequest\|requesting]] script.		\|caveats=*This events will be triggered in every script in the prim, not just in the [[llHTTPRequest\|requesting]] script.
	*It is ''not'' guaranteed that there will be an [[http_response]] for every [[llHTTPRequest]]().		*It is ''not'' guaranteed that there will be an [[http_response]] for every [[llHTTPRequest]]().

ObviousAltIsObvious Resident: move caution to the script it applies to

2016-09-18T23:36:27Z

move caution to the script it applies to

← Older revision		Revision as of 16:36, 18 September 2016
Line 29:		Line 29:
	**If the script moves to a different region before the remote HTTP server can respond, the response will be lost. [https://lists.secondlife.com/pipermail/secondlifescripters/2011-August/006309.html]		**If the script moves to a different region before the remote HTTP server can respond, the response will be lost. [https://lists.secondlife.com/pipermail/secondlifescripters/2011-August/006309.html]
	\|examples=		\|examples=
	{{LSL Tip\|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.}}
	<source lang="lsl2">		<source lang="lsl2">
	key http_request_id;		key http_request_id;
Line 81:		Line 80:
	</source>		</source>
	Another Example:		Another Example:
			{{KBcaution\|Remember to release URLs that you have requested! They are region resources just like prims, and it is possible to use them all and break other scripts.}}
	<source lang="lsl2">		<source lang="lsl2">
	string url;		string url;

Lady Sumoku: Replaced old block with

2015-01-22T08:33:41Z

Replaced old <LSL> block with <source lang="lsl2">

← Older revision		Revision as of 01:33, 22 January 2015
Line 30:		Line 30:
	\|examples=		\|examples=
	{{LSL Tip\|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 Tip\|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~~>		<source lang="lsl2">
	key http_request_id;		key http_request_id;

Line 48:		Line 48:
	}		}
	}		}
	</~~lsl~~>		</source>
	To parse POST content:		To parse POST content:
	<~~lsl~~>		<source lang="lsl2">
	string get_post_value(string content, string returns)		string get_post_value(string content, string returns)
	{		{
Line 79:		Line 79:
	return "";		return "";
	}		}
	</~~lsl~~>		</source>
	<~~lsl~~>		Another Example:
			<source lang="lsl2">
	string url;		string url;
	key urlRequestId;		key urlRequestId;
Line 184:		Line 185:
	}		}
	}		}
	</~~lsl~~>		</source>
	\|helpers		\|helpers
	\|also_header		\|also_header

Strife Onizuka at 04:39, 10 January 2014

2014-01-10T04:39:07Z

← Older revision		Revision as of 21:39, 9 January 2014
Line 1:		Line 1:
	{{LSL_Event\|event_id=32\|event_delay\|event=http_response		{{LSL_Event\|event_id=32\|event_delay\|event=http_response
	\|p1_type=key\|p1_name=request_id\|p1_desc=Matches return from [[llHTTPRequest]]		\|p1_type=key\|p1_subtype=handle\|p1_name=request_id\|p1_desc=Matches return from [[llHTTPRequest]]
	\|p2_type=integer\|p2_name=status\|p2_desc=[https://en.wikipedia.org/wiki/List_of_HTTP_status_codes HTTP status code] (like 404 or 200)		\|p2_type=integer\|p2_name=status\|p2_desc=[https://en.wikipedia.org/wiki/List_of_HTTP_status_codes HTTP status code] (like 404 or 200)
	\|p3_type=list\|p3_name=metadata\|p3_desc=List of HTTP_* constants and attributes		\|p3_type=list\|p3_name=metadata\|p3_desc=List of HTTP_* constants and attributes

Kireji Haiku at 16:07, 31 December 2013

2013-12-31T16:07:03Z

← Older revision		Revision as of 09:07, 31 December 2013
Line 1:		Line 1:
	{{LSL_Event\|event_id=32\|event_delay\|event=http_response		{{LSL_Event\|event_id=32\|event_delay\|event=http_response
	\|p1_type=key\|p1_name=request_id\|p1_desc=Matches return from [[llHTTPRequest]]		\|p1_type=key\|p1_name=request_id\|p1_desc=Matches return from [[llHTTPRequest]]
	\|p2_type=integer\|p2_name=status\|p2_desc=HTTP code (like 404 or 200)		\|p2_type=integer\|p2_name=status\|p2_desc=[https://en.wikipedia.org/wiki/List_of_HTTP_status_codes HTTP status code] (like 404 or 200)
	\|p3_type=list\|p3_name=metadata\|p3_desc=List of HTTP_* constants and attributes		\|p3_type=list\|p3_name=metadata\|p3_desc=List of HTTP_* constants and attributes
	\|p4_type=string\|p4_name=body\|p4_desc		\|p4_type=string\|p4_name=body\|p4_desc
Line 19:		Line 19:
	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.		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.
	<h3>Status 499</h3>		<h3>Status 499</h3>
	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:		Besides the usual [https://en.wikipedia.org/wiki/List_of_HTTP_status_codes HTTP status codes], SL implements a special {{LSLP\|status}} code 499. This code isn't generated by the remote web server but by SL's servers (see [[Simulator_IP_Addresses]]), it can indicate:
	*Request timeout (60 seconds)		*Request timeout (60 seconds)
	*SSL failure		*SSL failure
	*A space was present in the url (escape your URL with [[llEscapeURL]]).		*A space was present in the url (escape your URL with [[llEscapeURL]]).
	<h3>Status 502</h3>		<h3>Status 502</h3>
	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]].		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]] [[llHTTPResponse#Caveats\|in time]].
	\|caveats=*This events will be triggered in every script in the prim, not just in the [[llHTTPRequest\|requesting]] script.		\|caveats=*This events will be triggered in every script in the prim, not just in the [[llHTTPRequest\|requesting]] script.
	*It is ''not'' guaranteed that there will be an [[http_response]] for every [[llHTTPRequest]]().		*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. [https://lists.secondlife.com/pipermail/secondlifescripters/2011-August/006309.html]		**If the script moves to a different region before the remote HTTP server can respond, the response will be lost. [https://lists.secondlife.com/pipermail/secondlifescripters/2011-August/006309.html]
	\|examples=		\|examples=
			{{LSL Tip\|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>		<lsl>
	key http_request_id;		key http_request_id;
Line 79:		Line 80:
	}		}
	</lsl>		</lsl>
	{{LSL Tip\|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>		<lsl>
	string url;		string url;
Line 198:		Line 198:
	===Unicode===		===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 [http://www.w3.org/International/O-HTTP-charset W3C:Setting the HTTP charset parameter] for further details.		When serving content with UTF-8 characters be sure your server sets the outgoing <code>Content-Type</code> header so that it includes <code>charset=utf-8</code> otherwise it will be interpreted incorrectly. See [http://www.w3.org/International/O-HTTP-charset W3C:Setting the HTTP charset parameter] for further details.

	===Request Headers===		===Request Headers===

Kireji Haiku: changed one of the given examples to improve performance and readability and added another higher level example

2012-10-06T14:40:41Z

changed one of the given examples to improve performance and readability and added another higher level example

Show changes

Kaluura Boa: Typo!

2012-05-04T17:13:44Z

Typo!

← Older revision		Revision as of 10:13, 4 May 2012
Line 81:		Line 81:
	\|also_events		\|also_events
	\|also_functions={{LSL DefineRow\|\|[[llHTTPRequest]]}}		\|also_functions={{LSL DefineRow\|\|[[llHTTPRequest]]}}
	{{LSL DefineRow\|\|[[~~llHTTPResponset~~]]}}		{{LSL DefineRow\|\|[[llHTTPResponse]]}}
	\|also_articles		\|also_articles
	\|also_footer		\|also_footer

Kaluura Boa: Added a link to llHTTPResponse

2012-05-04T17:13:04Z

Added a link to llHTTPResponse

← Older revision		Revision as of 10:13, 4 May 2012
Line 81:		Line 81:
	\|also_events		\|also_events
	\|also_functions={{LSL DefineRow\|\|[[llHTTPRequest]]}}		\|also_functions={{LSL DefineRow\|\|[[llHTTPRequest]]}}
			{{LSL DefineRow\|\|[[llHTTPResponset]]}}
	\|also_articles		\|also_articles
	\|also_footer		\|also_footer

Cerise Resident at 01:36, 6 August 2011

2011-08-06T01:36:55Z

← Older revision		Revision as of 18:36, 5 August 2011
Line 27:		Line 27:
	\|caveats=*This events will be triggered in every script in the prim, not just in the [[llHTTPRequest\|requesting]] script.		\|caveats=*This events will be triggered in every script in the prim, not just in the [[llHTTPRequest\|requesting]] script.
	*It is ''not'' guaranteed that there will be an [[http_response]] for every [[llHTTPRequest]]().		*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.		**If the script moves to a different region before the remote HTTP server can respond, the response will be lost. [https://lists.secondlife.com/pipermail/secondlifescripters/2011-August/006309.html]
	\|examples=<lsl>key http_request_id;		\|examples=<lsl>key http_request_id;

← Older revision		Revision as of 21:39, 9 January 2014
Line 1:		Line 1:
	{{LSL_Event\|event_id=32\|event_delay\|event=http_response		{{LSL_Event\|event_id=32\|event_delay\|event=http_response
	\|p1_type=key\|p1_name=request_id\|p1_desc=Matches return from [[llHTTPRequest]]		\|p1_type=key\|p1_subtype=handle\|p1_name=request_id\|p1_desc=Matches return from [[llHTTPRequest]]
	\|p2_type=integer\|p2_name=status\|p2_desc=[https://en.wikipedia.org/wiki/List_of_HTTP_status_codes HTTP status code] (like 404 or 200)		\|p2_type=integer\|p2_name=status\|p2_desc=[https://en.wikipedia.org/wiki/List_of_HTTP_status_codes HTTP status code] (like 404 or 200)
	\|p3_type=list\|p3_name=metadata\|p3_desc=List of HTTP_* constants and attributes		\|p3_type=list\|p3_name=metadata\|p3_desc=List of HTTP_* constants and attributes