Share via


NonSecureProtocolRedirection Property of the IFPCRoutingRule Interface

The NonSecureProtocolRedirection property gets or sets a value from the FpcPublishProtocolRedirectionType enumerated type that specifies the protocol to use when redirecting (bridging) HTTP requests arriving on a nonsecure channel. The possible protocols are the Hypertext Transfer Protocol (HTTP) and Secure Sockets Layer (SSL) protocols.

C++

HRESULT put_NonSecureProtocolRedirection(
    FpcPublishProtocolRedirectionType FpcPublishProtocolRedirectionType
);
HRESULT get_NonSecureProtocolRedirection(
    FpcPublishProtocolRedirectionType* pPublishProtocolRedirectionType
);

Parameters

  • FpcPublishProtocolRedirectionType
    Value from the FpcPublishProtocolRedirectionType enumerated type that specifies the protocol to use when redirecting (bridging) HTTP requests arriving on a nonsecure channel.

  • pPublishProtocolRedirectionType
    Pointer to a variable that on return receives a value from the FpcPublishProtocolRedirectionType enumerated type specifying the protocol to use when redirecting (bridging) HTTP requests arriving on a nonsecure channel.

Return Value

These property methods return S_OK if the call is successful; otherwise, they return an error code.

Visual Basic

Property NonSecureProtocolRedirection As FpcPublishProtocolRedirectionType

Property Value

Value from the FpcPublishProtocolRedirectionType enumerated type that specifies the protocol to use when redirecting (bridging) HTTP requests arriving on a nonsecure channel.

Remarks

This property is read/write. Its default value is fpcHTTP, which indicates that redirected HTTP requests arriving on a nonsecure channel are routed using the HTTP protocol.

Requirements

Client Requires Windows 7 or Windows Vista.
Server Requires Windows Server 2008 R2 or Windows Server 2008 x64 Edition with SP2.
Version Requires Forefront Threat Management Gateway (TMG) 2010.
IDL

Declared in Msfpccom.idl.

DLL

Requires Msfpccom.dll.

See Also

FPCRoutingRule

Send comments about this topic to Microsoft

Build date: 6/30/2010