UniBasic Commands Reference - Rocket Software

If the response status indicates that redirection is needed (status 301, 302, 305 or
307), it will be performed automatically, up to five consecutive redirections (the limit
is set to prevent looping, suggested by RFC 2616).
If the response status is 401 or 407 (access denied), the response headers will be
examined to see if the server requires (or accepts) Basic authentication. If no Basic
authentication request is found, the function will return with an error. Otherwise
default Authentication (set by setHTTPDefault) will be used to resend the request.
If no default authentication is set, and no other cached user authentication is found,
the function will return with an error.
If the user provides authentication information through “Authorization” or “Proxy-
Authorization” header, the encoded information is cached. If later, a Basic authentication
request is raised, no default authentication is found, and only one
user/password encoding is cached, then it will be used to resend the request.
The response from the HTTP server is disposed into response_header and
response_data. It is the user’s responsibility to parse the headers and data. UniBasic
only performs transfer encoding (chunked encoding), and nothing else is done on the
data. In other words, content-encoding (gzip, compress, deflate, and so forth) are
supposed to be handled by the user, as with all MIME types.
Also, if a response contains header “Content-type: multipart/*”, all the data (multiple
bodies enclosed in “boundary delimiters”, see RFC 2046) will be stored in
response_data. It is the user’s responsibility to parse it according to “boundary”
parameter.
Parameters
The following table describes each parameter of the syntax.
Parameter Description
1-876 UniBasic Commands Reference
request_handle The handle to the request.
time_out The timeout value (in milliseconds) before the wait response is
abandoned.
post_data The data sent with the POST request.
submitRequest Parameters