Open HTTP Handle (G Dataflow)

Download Manual | Offline Viewer Required

Version:

Last Modified: December 18, 2017

Opens a client handle. Use client handles to wire together multiple HTTP nodes while preserving authentication credentials, HTTP headers, and cookies.

Inputs/Outputs
Compatibility

cookie file

Path that allows you to store a client-side cookie. Cookies store data across multiple web requests.

Cookie File Storage

HTTP nodes on the Web Server target store and maintain cookies that a server creates based on the browser environment and server configurations. The HTTP nodes cannot observe the cookies a server creates or add additional cookies to send to the server. You must set cookie file to an empty path or not a path.

On non-Web Server targets, you must manually specify how to manage the cookies the server creates. If you do not add a cookie file path or extract the cookies from the headers output, you cannot include the cookies in subsequent requests to the server.

username

Log-in username for the SMTP server you specify. On most public servers, this is your email address.

password

Log-in password for the SMTP server you specify.

error in

Error conditions that occur before this node runs.

The node responds to this input according to standard error behavior.

Standard Error Behavior

Many nodes provide an error in input and an error out output so that the node can respond to and communicate errors that occur while code is running. The value of error in specifies whether an error occurred before the node runs. Most nodes respond to values of error in in a standard, predictable way.

error in does not contain an error	error in contains an error

If no error occurred before the node runs, the node begins execution normally. If no error occurs while the node runs, it returns no error. If an error does occur while the node runs, it returns that error information as error out.	If an error occurred before the node runs, the node does not execute. Instead, it returns the error in value as error out.

Default: No error

verify server

Boolean value that determines whether to verify the server's identity and establish a secure connection. Use this input to allow HTTP nodes to communicate using the HTTPS protocol.

True	Verifies the servers identity and establishes a secure connection.
False	Does not verify the servers identity or establish a secure connection.

Server Verification on a Web Server Target

HTTP nodes on a Web Server target do not allow you to configure verification of HTTPS servers. You must set this input to True. To work around server verification, you must configure your browser or operating system to connect to servers that you cannot verify.

Default: True

client handle out

Unique value that identifies the web request. Use this value to refer to this web request in subsequent node calls.

You can use the same client handle to wire together multiple HTTP nodes to preserve authentication credentials, HTTP headers, and cookies.

Client handles are not required when making independent web requests without persistent data such as headers or credentials.

error out

Error information.

The node produces this output according to standard error behavior.

Standard Error Behavior

error in does not contain an error	error in contains an error

If no error occurred before the node runs, the node begins execution normally. If no error occurs while the node runs, it returns no error. If an error does occur while the node runs, it returns that error information as error out.	If an error occurred before the node runs, the node does not execute. Instead, it returns the error in value as error out.

Where This Node Can Run:

Desktop OS: Windows

FPGA: This product does not support FPGA devices

Web Server: Supported in VIs that run in a web application

Table Of Contents