| name | The key of the header to be set. Case-sensitive. |
| value | The header's intended value. |
Set a HTTP request header to a custom value.
Header keys and values must be valid according to RFC 2616. Neither string may contain certain illegal characters, such as control characters. Both strings must be non-null and contain a minimum of 1 character. For more information, see RFC 2616, section 4.2.
This method cannot be called after Send has been called.
These headers cannot be set with custom values on any platform: accept-charset, access-control-request-headers, access-control-request-method, connection, date, dnt, expect, host, keep-alive, origin, referer, te, trailer, transfer-encoding, upgrade, via.
It is possible to set a custom value for the accept-encoding header but the resulting behavior is unreliable so it is strongly recommended to let it be automatically handled unless you can accept the risk of unexpected results.
The content-length header will be automatically populated based on the contents of the attached DownloadHandler, if any, and cannot be set to a custom value.
The x-unity-version header is automatically set by Unity and may not be set to custom value.
The user-agent header is automatically set by Unity and it is not recommended to set it to custom value.
The cookie and cookie2 headers are automatically managed by underlaying cookie engine. While exact behavior is platform dependent, usually setting cookies via this header will append them to those set by engine. See Also: ClearCookieCache.
In addition to the above, the following headers are filled by the web browser on the WebGL platform, and therefore may not have custom values set: cookie, cookie2, user-agent.
Did you find this page useful? Please give it a rating: