Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All

2.2.2 URI Encoding

The format of the URI header field of the HTTP request has a special interpretation in this protocol. As specified in [RFC2616], the URI is to be of the following form.

 http_URL = "http:" "//" host [ ":" port ] [ abs-path 
 [ "?" query ]]

This protocol specifies that abs-path MUST be present for RPC over HTTP v2 and MUST have the following form.

 nocert-path = "/rpc/rpcproxy.dll"
 withcert-path = "/rpcwithcert/rpcproxy.dll"
 abs-path = nocert-path / withcert-path

The form matching withcert-path MUST be used whenever the client authenticates to the HTTP server using a client-side certificate. The form matching nocert-path MUST be used in all other cases.<13>

This protocol specifies that query string MUST be present for RPC over HTTP v2 and MUST be of the following form.

 query = server-name ":" server-port

The inbound proxy or outbound proxy uses the query string to establish a connection to an RPC over the HTTP server, as specified in sections and

 server-name = DNS_Name / IP_literal_address / 
               IPv6_literal_address / NetBIOS_Name
 server-port = 1*6(DIGIT)

The length of server-name MUST be less than 1,024 characters.

DNS_Name: An Internet host name or IP_literal_address that is the string representation of an IP literal address, as specified in [RFC1123] section 2.1.

IPv6_literal_address: MUST be the string representation of an IPv6 literal address as specified in [RFC4291] section 2.

NetBIOS_Name: MUST be a NetBIOS name. For more details about NetBIOS, refer to [NETBEUI], [RFC1001], and [RFC1002].

© 2015 Microsoft