Configure SSL (G Dataflow)

Path to a private key file that is part of the client certificate and client authentication process.

Password for the private key file. If the private key file is not encrypted, you do not have to specify a private key password.

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.

Path to a list of trusted certificate authority (CA) certificates. If you specify True for the verify server input, the client verifies the server's identity against this list of trusted certificates.

Path to the client certificate file for servers that require client authentication. Some servers require this file to verify the identity of the client by using a trusted CA.

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

A Boolean value that checks the server's certificate against the list of trusted CA certificates specified by the CA certificate file input.

Default: True

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 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.