Table Of Contents

Configure CORS (G Dataflow)

Last Modified: June 25, 2019

Includes user credentials in cross-origin HTTP requests to servers that require credentials.

Use this node with the Open HTTP Handle node to create cross-origin HTTP requests that include user credentials such as HTTP cookies, HTTP authentication headers, or TLS client certificates. This node has no effect on same-origin HTTP requests, which always include user credentials.

Programming Patterns

Considerations When Accessing Data on Servers

connector_pane_image
datatype_icon

client handle

Unique value that identifies the web request.

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

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

datatype_icon

include credentials during CORS

Boolean value that determines whether to include credentials such as HTTP cookies, HTTP authentication headers, or TLS client certificates in a cross-origin HTTP request.

True Credentials are included in HTTP requests associated with this client handle.
False Credentials are not included in HTTP requests associated with this client handle.

Default: False

datatype_icon

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

datatype_icon

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 and HTTP headers.

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

datatype_icon

error out

Error information.

The node produces this output 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.

Where This Node Can Run:

Desktop OS: Windows

FPGA: Not supported

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


Recently Viewed Topics