You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 28, 2024. It is now read-only.
Sets a custom HTTP header to be prepared for use when llHTTPResponse() is called.
request_id: the key of the request for which a header should be prepared.
header: the name of the header to set. May not be used to override to certain headers as doing so will produce an error, as will attempting to specify a header name including invalid characters.
value: the value to set within the header.
In essence this function behaves a lot like setting HTTP_CUSTOM_HEADER on an llHTTPRequest(), but will added up to 8 headers (each no more than 254 characters combined) to be sent as part of an llHTTPResponse().
Why is this feature important to you? How would it benefit the community?
The ability to return custom headers is a very useful alternative to having to place all data in the response's body, significantly cutting down on the amount of processing required at the other end (since all good HTTP processors handle headers automatically).
It seems strange to have this capability for llHTTPRequest() but not for llHTTPResponse(), so adding it via this function should improve consistency between the two.
Original Jira Fields
Field
Value
Issue
BUG-40654
Summary
llSetHTTPHeader() - Enable setting of headers in http_response()
Type
New Feature Request
Priority
Unset
Status
Closed
Resolution
Unactionable
Reporter
Haravikk Mistral (haravikk.mistral)
Created at
2016-10-07T10:04:34Z
Updated at
2016-10-12T18:42:31Z
{
'Business Unit': ['Platform'],
'Date of First Response': '2016-10-12T13:42:31.690-0500',
'How would you like the feature to work?': '{code}llSetHTTPHeader(key request_id, string header, string value);{code}\r\nSets a custom HTTP header to be prepared for use when [{{llHTTPResponse()}}|https://wiki.secondlife.com/wiki/LlHTTPResponse] is called.\r\n\r\n* *request_id*: the key of the request for which a header should be prepared.\r\n* *header*: the name of the header to set. May not be used to override to certain headers as doing so will produce an error, as will attempting to specify a header name including invalid characters.\r\n* *value*: the value to set within the header.\r\n\r\nIn essence this function behaves a lot like setting {{HTTP_CUSTOM_HEADER}} on an [{{llHTTPRequest()}}|https://wiki.secondlife.com/wiki/LlHTTPRequest], but will added up to 8 headers (each no more than 254 characters combined) to be sent as part of an {{llHTTPResponse()}}.',
'ReOpened Count': 0.0,
'Severity': 'Unset',
'Target Viewer Version': 'viewer-development',
'Why is this feature important to you? How would it benefit the community?': "The ability to return custom headers is a very useful alternative to having to place all data in the response's body, significantly cutting down on the amount of processing required at the other end (since all good HTTP processors handle headers automatically).\r\n\r\nIt seems strange to have this capability for {{llHTTPRequest()}} but not for {{llHTTPResponse()}}, so adding it via this function should improve consistency between the two.",
}
The text was updated successfully, but these errors were encountered:
How would you like the feature to work?
Sets a custom HTTP header to be prepared for use when
llHTTPResponse()
is called.request_id: the key of the request for which a header should be prepared.
header: the name of the header to set. May not be used to override to certain headers as doing so will produce an error, as will attempting to specify a header name including invalid characters.
value: the value to set within the header.
In essence this function behaves a lot like setting
HTTP_CUSTOM_HEADER
on anllHTTPRequest()
, but will added up to 8 headers (each no more than 254 characters combined) to be sent as part of anllHTTPResponse()
.Why is this feature important to you? How would it benefit the community?
The ability to return custom headers is a very useful alternative to having to place all data in the response's body, significantly cutting down on the amount of processing required at the other end (since all good HTTP processors handle headers automatically).
It seems strange to have this capability for
llHTTPRequest()
but not forllHTTPResponse()
, so adding it via this function should improve consistency between the two.Original Jira Fields
The text was updated successfully, but these errors were encountered: