IFPCWebPublishingProperties::PublishedServerType property
Applies to: desktop apps only
The PublishedServerType property gets or sets a value from the FpcPublishedServerType enumerated type that indicates how requests are to be forwarded to the Web server published by the rule.
This property is read/write.
Syntax
HRESULT put_PublishedServerType(
FpcPublishedServerType ServerType
);
HRESULT get_PublishedServerType(
FpcPublishedServerType *pServerType
);
' Data type: FpcPublishedServerType
Property PublishedServerType( _
ByVal ServerType As FpcPublishedServerType, _
ByVal pServerType As FpcPublishedServerType _
) As FpcPublishedServerType
Property value
Value from the FpcPublishedServerType enumerated type. The possible values are:
- fpcWebServerThruHTTP, which indicates that incoming HTTP and HTTPS requests are to be forwarded to the published Web server on the port specified in the HTTPRedirectPort property using the HTTP protocol.
- fpcWebServerThruSSL, which indicates that incoming HTTP and HTTPS requests are to be forwarded over a secure channel to the published Web server on the port specified in the SSLRedirectPort property using the HTTPS protocol.
- fpcWebServerThruBothHTTPAndSSL, which indicates that incoming HTTP requests are to be forwarded to the published Web server on the port specified in the HTTPRedirectPort property using the HTTP protocol and that HTTPS requests are to be forwarded over a secure channel to the published Web server on the port specified in the SSLRedirectPort property using the HTTPS protocol.
- fpcFTPServer, which indicates that incoming FTP requests are to be forwarded to the published Web server on the port specified in the FTPRedirectPort property using the FTP protocol.
Error codes
These property methods return S_OK if the call is successful; otherwise, they return an error code.
Remarks
This property is read/write. Its default value is fpcWebServerThruHTTP, which indicates that incoming HTTP and HTTPS requests are to be forwarded to the published Web server on the port specified in the HTTPRedirectPort property using the HTTP protocol.
a Forefront TMG computer performs SSL bridging whenever it terminates or initiates an SSL connection on a segment between a client and the published Web server. The following SSL bridging scenarios are possible:
- An HTTP request is forwarded over an SSL connection. In this scenario, the client sends an unencrypted request for an HTTP object. Forefront TMG encrypts the request and forwards it to the Web server. The Web server returns the encrypted object to the Forefront TMG computer. Then, Forefront TMG decrypts the object and sends it to the client.
- A request arriving on an SSL connection is forwarded over an SSL connection. In this scenario, the client sends an encrypted request. Forefront TMG decrypts the request, and then encrypts it again and forwards it to the Web server. The Web server returns the encrypted object to the Forefront TMG computer. Forefront TMG decrypts the object, encrypts it again, and sends it to the client.
- A request arriving on an SSL connection is forwarded as an HTTP request. In this scenario, the client sends an encrypted request. Forefront TMG decrypts the request and forwards it to the Web server. The Web server returns the HTTP object to the Forefront TMG computer. Forefront TMG encrypts the object and sends it to the client. In other words,
Requirements
Minimum supported client |
Windows Vista |
Minimum supported server |
Windows Server 2008 R2, Windows Server 2008 with SP2 (64-bit only) |
Version |
Forefront Threat Management Gateway (TMG) 2010 |
IDL |
Msfpccom.idl |
DLL |
Msfpccom.dll |
See also
Build date: 7/12/2010