Table Of Contents

Add Header (G Dataflow)

Version:
    Last Modified: October 2, 2017

    Adds a header field line to all web requests. Headers define attributes of the data exchanged between the client and server.

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

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

    datatype_icon

    header

    Header field that adds all web requests associated with the client handle. The header input provides a pull-down menu with available header fields.

    If you specify a header that already exists, the specified value overwrites the header value.

    datatype_icon

    value

    Value to assign to the header field.

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

    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: This product does not support FPGA devices

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


    Recently Viewed Topics