3.1.1.4.1 Opening a Connection

When an implementation of a higher-level protocol calls an implementation of the RPC over HTTP Protocol to open a new connection to the server, this protocol MUST perform the following sequence of steps:

  • Send an RPC connect HTTP request as specified in section 2.1.1.1.1. The server-name component of the URI as defined in section 2.2.2 SHOULD be the network address given to RPC. The endpoint given to RPC will be placed in the server-port component of the URI as defined in section 2.2.2. Thus, the created HTTP request MUST be sent to a mixed proxy whose name is extracted from the network options given to the RPC runtime in an implementation-specific way.

  • Move to a wait state and wait until a network event or a timeout occurs.

The protocol MUST treat any status code in the range 200 to 299, inclusive, as an indication of success. Any other status code MUST be treated by the protocol as a connection error and be processed as specified in section 3.1.3.4.3. If no RPC connect response is received (as specified in section 2.1.1.1.2) before the timeout occurs, the protocol MUST treat this as a connection error and process it as specified in section 3.1.3.4.3.

If a connection is successfully opened, the protocol MUST cancel the Connection Setup timer.