The NoCompressionForSpecifiedContentTypes property gets or sets a Boolean value that indicates whether HTTP compression is allowed for all content types except the content type sets referenced by the CompressibleContentTypeSets property or is allowed only for the content type sets referenced by the CompressibleContentTypeSets property.
HRESULT put_NoCompressionForSpecifiedContentTypes( VARIANT_BOOL fExcludeSpecifiedContentTypes ); HRESULT get_NoCompressionForSpecifiedContentTypes( VARIANT_BOOL* pfExcludeSpecifiedContentTypes );
Pointer to a Boolean variable that is set on return to VARIANT_TRUE is allowed for all content types except the content type sets referenced by the CompressibleContentTypeSets property, or to VARIANT_FALSE if HTTP compression is allowed only for the content type sets referenced by the CompressibleContentTypeSets property.
Boolean value that indicates whether HTTP compression is allowed for all content types except the content type sets referenced by the CompressibleContentTypeSets property or is allowed only for the content type sets referenced by the CompressibleContentTypeSets property.
These property methods return S_OK if the call is successful; otherwise, they return an error code.
Property NoCompressionForSpecifiedContentTypes As Boolean
Boolean value that indicates whether HTTP compression is allowed for all content types except the content type sets referenced by the CompressibleContentTypeSets property or is allowed only for the content type sets referenced by the CompressibleContentTypeSets property.
This property is read/write. Its default value is False (VARIANT_FALSE in C++), which indicates that HTTP compression is allowed only for the content type sets referenced by the CompressibleContentTypeSets property.
Client | Requires Windows Vista or Windows XP. |
---|---|
Server | Requires Windows Server 2008. |
Version | Requires Forefront Threat Management Gateway (TMG). |
IDL |
Declared in Msfpccom.idl. |
DLL |
Requires Msfpccom.dll. |
FPCHTTPCompressionConfiguration
Send comments about this topic to Microsoft
Build date: 11/30/2009
© 2008 Microsoft Corporation. All rights reserved.