Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The SecureProtocolRedirection property gets or sets a value from the FpcPublishProtocolRedirectionType enumerated type that specifies the protocol to use when redirecting (bridging) SSL requests that came on a secure channel. The possible protocols are the Hypertext Transfer Protocol (HTTP) and Secure Sockets Layer (SSL) protocols.
C++
HRESULT put_SecureProtocolRedirection(
FpcPublishProtocolRedirectionType PublishProtocolRedirectionType
);
HRESULT get_SecureProtocolRedirection(
FpcPublishProtocolRedirectionType* pPublishProtocolRedirectionType
);
Parameters
PublishProtocolRedirectionType
Value from the FpcPublishProtocolRedirectionType enumerated type that specifies the protocol to use when redirecting (bridging) SSL requests arriving on a secure 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) SSL requests arriving on a secure channel.
Return Value
These property methods return S_OK if the call is successful; otherwise, they return an error code.
Visual Basic
Property SecureProtocolRedirection As FpcPublishProtocolRedirectionType
Property Value
Value from the FpcPublishProtocolRedirectionType enumerated type that specifies the protocol to use when redirecting (bridging) SSL requests arriving on a secure channel.
Remarks
This property is read/write. Its default value is fpcSSL, which indicates that redirected SSL requests arriving on a secure channel are routed using the SSL 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
Send comments about this topic to Microsoft
Build date: 6/30/2010