This topic has not yet been rated - Rate this topic

HSE_REQ_MAP_URL_TO_PATH

IIS 6.0

This support function allows your ISAPI extension to map a logical URL path to a physical path.

Note:
This support function was reported to have been deprecated in IIS version 5.1 in favor of HSE_REQ_MAP_URL_TO_PATH_EX, but that is not the case. HSE_REQ_MAP_URL_TO_PATH_EX is useful only to DAV programmers. The path size of the HSE_URL_MAPEX_INFO structure which is used by HSE_REQ_MAP_URL_TO_PATH_EX is limited to MAX_PATH length.

BOOL ServerSupportFunction(
   HCONN ConnID,
   DWORD dwServerSupportFunction,
   LPVOID lpvBuffer,
   LPDWORD lpdwSizeofBuffer,
   LPDWORD NULL
);

ConnID: Specifies the connection identifier of the client to which the response data should be sent.
dwServerSupportFunction: The name of the Server Support function, which in this case must be set to HSE_REQ_MAP_URL_TO_PATH
lpvBuffer: Points to a buffer that should contain the URL to map upon entry, and will contain the physical path upon return.
lpdwSizeofBuffer: Points to a buffer that will contain the size of the physical path pointed to by lpvBuffer upon return. If the physical path is too large for lpvBuffer, GetLastError returns ERROR_INSUFFICIENT_BUFFER, and lpdwSizeofBuffer contains the number of bytes needed to store the physical path so that you can make the call again with a larger lpvBuffer.
NULL: Must be set to NULL.

Examples of virtual-to-physical path mappings include:

Client: Requires Windows XP Professional, Windows 2000 Professional, or Windows NT Workstation 4.0.

Server: Requires Windows Server 2003, Windows 2000 Server, or Windows NT Server 4.0.

Product: IIS

Header: Declared in httpext.h.

Did you find this helpful? Yes No

Not accurate

Not enough depth

Need more code examples

(1500 characters remaining)