SkipNameResolutionForWebPublishingRules Property of the IFPCWebProxy Interface

The SkipNameResolutionForWebPublishingRules property gets or sets a Boolean value that indicates whether the Forefront TMG Web proxy will skip name resolution while checking Web publishing rules.

C++

HRESULT put_SkipNameResolutionForWebPublishingRules(
    VARIANT_BOOL fSkipNameResolutionForWebPublishingRules
);
HRESULT get_SkipNameResolutionForWebPublishingRules(
    VARIANT_BOOL* pfSkipNameResolutionForWebPublishingRules
);

Parameters

  • fSkipNameResolutionForWebPublishingRules
    Boolean value that specifies whether the Web proxy will skip name resolution while checking Web publishing rules.

  • pfSkipNameResolutionForWebPublishingRules
    Pointer to a Boolean variable that is set on return to VARIANT_TRUE if the Web proxy will skip name resolution while checking Web publishing rules, or to VARIANT_FALSE if the Web proxy will not skip name resolution while checking Web publishing rules.

Return Value

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

Visual Basic

Property SkipNameResolutionForWebPublishingRules As Boolean

Property Value

Boolean value that indicates whether the Web proxy will skip name resolution while checking Web publishing rules.

Remarks

This property is read/write. Its default value is True (VARIANT_TRUE in C++).

After the value of this property has been modified, the change must be written to persistent storage by calling the Save method, and the Microsoft Firewall service must be restarted for the change to take effect. For more information about restarting the Firewall service to apply changes, see Restarting Services After Configuration Changes.

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

FPCWebProxy

Send comments about this topic to Microsoft

Build date: 6/30/2010