UniBasic Commands Reference - Rocket Software

1-86 UniBasic Commands Reference
Return
Code Status
1 Invalid request handle.
2 Invalid parameter.
3 Bad content type.
addRequestParameter Return Codes (continued)
Note: For a GET request, content_handling is ignored.
For a POST request with default content type, the default for content_handling is
“Content-Type:text/plain” if content_handling is not specified. For a POST request
with “Multipart/*” content-type, content_handling is a dynamic array containing
Content-* strings separated by field marks (@FM). They will be included in the
multipart message before the data contained in parameter_value is sent. An example
of content_handling:
Content-Type: application/XML @FM
Content-Dispostion: attachment; file=”C:\drive\test.dat” @FM
Content-Length: 1923
Specifically, for a POST request with content type “multipart/form-data”, a
“Content-Dispostion: form-data” header will be created (or, in the case of Content-
Dispostion already in content_handling, “form-data” will be added to it).
For both a GET and a POST request with either no content type specified or specified
as “application/x-www-form-urlencoded”, as described in createRequest(), URL
encoding is performed on data in parameter_value automatically. Basically, any
character other than alpha-numeric is considered “unsafe” and will be replaced by
%HH where HH is the ASCII value of the character in question. For example, ‘#’ is
replaced by %23, and ‘/’ is replaced by %2F, etc.. One exception is that by
convention, spaces (‘ ‘) are converted into ‘+’.
For a POST method with other MIME-type specified, no encoding is done on data
contained in parameter_value.