UniBasic Commands Reference - Rocket Software

UniBasic Commands Reference - Rocket Software UniBasic Commands Reference - Rocket Software

rocketsoftware.com
from rocketsoftware.com More from this publisher
11.04.2013 Views

createSecureRequest Syntax createSecureRequest(URL, http_method, request_handle, security_context) Description The createSecureRequest function behaves exactly the same as the createRequest() function, except for the fourth parameter, a handle to a security context, which is used to associate the security context with the request. If the URL does not start with “https” the parameter is ignored. If the URL starts with “https” but an invalid context handle or no handle is provided, the function aborts and returns with an error status. Parameters The following table describes each parameter of the syntax. Parameter Description 1-183 UniBasic Commands Reference URL A string containing the URL for a resource on a web server. An accepted URL must follow the specified syntax defined in RFC 1738. The general format is: http://:/?. The host can be either a name string or IP address. The port is the port number to connect to, which usually defaults to 80 and is often omitted, along with the preceding colon. The path tells the web server which file you want, and, if omitted, means “home page” for the system. The searchpart can be used to send additional information to a web server. http_method A string which indicates the method to be performed on the resource. See the table below for the available (case-sensitive) methods. request_handle A handle to the request object. securityContext A handle to the security context. createSecureRequest Parameters

The following table describes the available methods for http_method. Method Description GET Retrieves whatever information, in the form of an entity, identified by the Request-URI. If the Request-URI refers to a data-producing process, it is the produced data which shall be returned as the entity in the response and not the source text of the process, unless that text happens to be the output of the process. POST [:] For this method, it can also have an optional MIME-type to indicate the content type of the data the request intends to send. If no MIME-type is given, the default content type will be “application/x-wwwform-urlencoded”. Currently, only “multipart/form-data” is internally supported, as described in function addRequestParameter() and submitRequest(), although other “multipart/* data can also be sent if the user can assemble it on his/her own. (The multipart/form-data format itself is thoroughly described in RFC 2388). HEAD The HEAD method is identical to GET except that the server MUST NOT return a message-body in the response. The metainformation contained in the HTTP headers in response to a HEAD request SHOULD be identical to the information sent in response to a GET request. This method can be used for obtaining metainformation about the entity implied by the request without transferring the entity-body itself. This method is often used for testing hypertext links for validity, accessibility, and recent modification. OPTIONS The OPTIONS method represents a request for information about the communication options available on the request/response chain identified by the Request-URI. This method allows the client to determine the options and/or requirements associated with a resource, or the capabilities of a server, without implying a resource action or initiating a resource retrieval. HTTP 1.1 and later. DELETE The DELETE method requests that the origin server delete the resource identified by the Request-URI. HTTP 1.1 and later. createRequest Methods createSecureRequest 1-184

createSecureRequest<br />

Syntax<br />

createSecureRequest(URL, http_method, request_handle, security_context)<br />

Description<br />

The createSecureRequest function behaves exactly the same as the<br />

createRequest() function, except for the fourth parameter, a handle to a security<br />

context, which is used to associate the security context with the request. If the URL<br />

does not start with “https” the parameter is ignored. If the URL starts with “https” but<br />

an invalid context handle or no handle is provided, the function aborts and returns<br />

with an error status.<br />

Parameters<br />

The following table describes each parameter of the syntax.<br />

Parameter Description<br />

1-183 <strong>UniBasic</strong> <strong>Commands</strong> <strong>Reference</strong><br />

URL A string containing the URL for a resource on a web server. An<br />

accepted URL must follow the specified syntax defined in RFC<br />

1738. The general format is:<br />

http://:/?. The host can be either a<br />

name string or IP address. The port is the port number to connect to,<br />

which usually defaults to 80 and is often omitted, along with the preceding<br />

colon. The path tells the web server which file you want, and,<br />

if omitted, means “home page” for the system. The searchpart can be<br />

used to send additional information to a web server.<br />

http_method A string which indicates the method to be performed on the resource.<br />

See the table below for the available (case-sensitive) methods.<br />

request_handle A handle to the request object.<br />

securityContext A handle to the security context.<br />

createSecureRequest Parameters

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!