Extensibility

Re: IIS 6.0: How to identify at runtime if extension is used in wildcard mapping

anilr — Wed, 01 Oct 2008 19:59:23 GMT

Yes, your understanding is correct. However, if you are doing server-side redirect (meaning the new url is different), either the new url would be mapped to something else or maybe you need to do further server-side redirect with the url if it is still mapped to your extension.

Re: IIS 6.0: How to identify at runtime if extension is used in wildcard mapping

rajivdk — Wed, 01 Oct 2008 19:45:04 GMT

Thanks for the reply.

As a follow-up question:

It looks like HSE_EXEC_URL_IGNORE_CURRENT_INTERCEPTOR works only with extensions used as wildcard mappings.

When I do a server-side redirect from an ISAPI dll configured as an application extension mapping, IIS sends back the request to the same DLL (does not ignore it) resulting in recursion.

Is my understanding correct that this flag will work only for wildcard mappings? Any workarounds?

-Rajiv.

Re: IIS 6.0: How to identify at runtime if extension is used in wildcard mapping

anilr — Wed, 01 Oct 2008 19:23:40 GMT

No, there is no way. Just create 2 different ISAPI extensions for the 2 tasks.

IIS 6.0: How to identify at runtime if extension is used in wildcard mapping

rajivdk — Wed, 01 Oct 2008 17:21:14 GMT

Hi,

I have an ISAPI extension that is used as an application extension mapping and now I am extending it to be used as a wildcard mapping as well (supporting server-side redirection using HSE_REQ_EXEC_URL).

Is there a way I can distinguish between the two (whether used in wildcard mapping or not), in my code at runtime?

The reason is, if my extension is mapped as an application extension, I do not want to use HSE_REQ_EXEC_URL. However, I do want to use it if my extension is used in a wildcard mapping.

Any suggestions?

Thanks,
-Rajiv.