Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
A version of this page is also available for
4/8/2010

This function is an application-defined function. It is the first entry-point function called by the Web Server on your ISAPI filter, and must be present for the filter to work properly. The Web Server passes a pointer to an HTTP_FILTER_VERSIONstructure, which can be used to supply important filter configuration information to the Web Server. The most important information passed to the Web Server is the bitmask that contains flags that specify which notification events your filter can process, and a flag that indicates the overall processing priority for your filter. The GetFilterVersionname for this function is a placeholder for the function name defined by the header.

Syntax 

BOOL WINAPI GetFilterVersion(
  PHTTP_FILTER_VERSION 
pVer
);

Parameters

pVer

[out] Pointer to the HTTP_FILTER_VERSIONstructure that contains both the version information for the server and members with which the filter can indicate filter version number, notifications, and priority desired.

Return Value

Returns TRUE if the function succeeds, and FALSE otherwise. This function must return TRUE for the filter to remain loaded and working properly.

Remarks

Due to performance considerations, it is important to register only for those notifications that are necessary for your filter's purposes.

Requirements

Header httpfilt.h
Library Developer Implemented
Windows Embedded CE Windows CE 3.0 and later
Windows Mobile Pocket PC 2000 and later, Smartphone 2002 and later

See Also

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.