Partager via

RPC over HTTP Proxy

  • Article

Applies To: Windows Server 2008

Remote procedure call (RPC) clients can use RPC over Hypertext Transfer Protocol (HTTP) to connect securely and efficiently across the Internet to RPC server programs and to execute remote procedure calls.

RPC over HTTP Proxy is a proxy that is used by objects that receive remote procedure calls over HTTP. Clients can use this proxy to discover these objects even if the objects are moved between servers or if they exist in discrete areas of the network, usually for security reasons.

The RPC over HTTP Proxy runs on an Internet Information Services (IIS) computer. It accepts RPC requests coming from the Internet, and it performs authentication, validation, and access checks on those requests. If a request passes all the tests, the RPC over HTTP Proxy forwards the request to the RPC server that performs the actual processing. With RPC over HTTP, the RPC client and server do not communicate directly. Instead, they use the RPC over HTTP Proxy as an intermediary.

Aspects

The following is a list of all aspects that are part of this managed entity:

Name Description

Remote Procedure Call (RPC) Load Balancing Service

The Remote Procedure Call (RPC) Load Balancing service is used with Terminal Services Gateway server. The administrator can configure the RPC Load Balancing service using the Terminal Server administrative tool.

Remote Procedure Call (RPC) Proxy Configuration

Remote Procedure Call (RPC) Proxy enables RPC over HTTP which you can use to make RPC calls using HTTP as the transport. RPC Proxy is required if you are using RPC over HTTP.

RPC over HTTP traffic is protected by standard RPC security and, in addition, it is protected by the tunneling mechanism provided by RPC over HTTP.

Application Server