Opens a client handle. Use client handles to wire together multiple HTTP Client VIs while preserving authentication credentials, HTTP headers, and cookies. You can specify a username and password, if necessary, to send Web requests to a server that requires authentication. You also can create a cookie file that stores data across multiple Web requests.


icon

Inputs/Outputs

  • cpath.png cookie file —

    cookie file is the path to store a client-side cookie. Cookies store data across multiple Web requests.

  • cstr.png username —

    username specifies the log-in username for the HTTP server you created earlier.

  • cstr.png password —

    password specifies the log-in password for the HTTP server.

  • cerrcodeclst.png error in (no error) —

    error in describes error conditions that occur before this node runs. This input provides standard error in functionality.

  • cbool.png verify server(true) —

    verify server (true) specifies whether to verify the server's identity and establish a secure connection. Use this control to allow HTTP Client VIs to communicate using the https:// protocol. The default value is TRUE.

  • idlrn.png client handle out —

    client handle out returns the client handle associated with the Web request. Use client handles to wire together multiple HTTP Client VIs while preserving authentication credentials, HTTP headers, and cookies. Client handles are not required when making independent Web requests without persistent data such as headers or credentials.

  • ierrcodeclst.png error out —

    error out contains error information. This output provides standard error out functionality.

    • Client handles increase network efficiency by limiting the number of network sockets and ports necessary to perform multiple Web requests. Client handles are not required when making independent Web requests without persistent data such as headers or credentials.

    The following screenshot shows code that performs the following:

    1. The OpenHandle VI opens a client handle and a client-side cookie that can store persistent data.
    2. The AddHeader VI adds a new header field line that sets the preferred language for subsequent Web requests associated with the client handle.
    3. The GET VI performs a Web request that includes the Accept-Language header.
    4. The CloseHandle VI closes the client handle and deletes any persistent data, including headers.