|
sponsored links |
|
|
sponsored links
|
|
1
16th August 18:24
External User
Posts: 1
|
Multiple ISAPI extensions problem
Hello
I have the following problem I have and ISAPI extension that is directly accessible by Inet clients of my IIS6 I also need another ISAPI extension set on Web Site level that I would like to process all requests including the ones that are sent to my main ISAPI Extension What I see currently is that requests to my main Extension are received unmodified so they are not passed tru the other ISAPI Extension (which works fine by its own) Is there any way I should set my IIS6 so requests to my main ISAPI are first processed by my Web Site level ISAPI Any configuration tricks are welcome Jivko |
|
|
|
2
16th August 18:24
External User
Posts: 1
|
Multiple ISAPI extensions problem
This can be accomplished by "Wildcard application mapping", which is an
ISAPI Extension configured to trigger on "all extensions", examine/modify the incoming request, and then pass the modification along to be executed. In your case, you can configure a wildcard application mapping at the Website level (and if you override the ScriptMap at child URLs/vdirs, you must reconfigure the wildcard mapping at those levels as well), which examines/modifies the incoming request and passes it along. Thus, when you make a request directly to your other ISAPI Extension, this website-level one will examine/modify the request first, and then pass it to your other ISAPI Extension. Please do the following: - Read product do***entation as well as IIS Architectural do***entation on "Wildcard application mapping" and how to configure them - MSDN Do***entation on HSE_REQ_EXEC_URL - Look at Platform SDK for IIS and sample code using HSE_REQ_EXEC_URL - Google this newsgroup for the many questions, answers, and sample code that have been posted regarding HSE_REQ_EXEC_URL http://www.microsoft.com/downloads/details.aspx?FamilyID=80a1b6e6-829e-49b7-8c02-333d9c148e69&DisplayLang=en http://www.microsoft.com/msdownload/platformsdk/sdkupdate/default.htm -- //David IIS This posting is provided "AS IS" with no warranties, and confers no rights. // Hello, I have the following problem I have and ISAPI extension that is directly accessible by Inet clients of my IIS6. I also need another ISAPI extension set on Web Site level that I would like to process all requests including the ones that are sent to my main ISAPI Extension. What I see currently is that requests to my main Extension are received unmodified so they are not passed tru the other ISAPI Extension (which works fine by its own). Is there any way I should set my IIS6 so requests to my main ISAPI are first processed by my Web Site level ISAPI? Any configuration tricks are welcome. Jivko |
|
|
|
3
16th August 18:24
External User
Posts: 1
|
Multiple ISAPI extensions problem
Hello David
The ISAPI that I have described as configured on Web Site level is defined as Wildcard Application Map. I do not know any other way to set an ISAPI Extension to process all requests on IIS 6. This works just fine by its own The strange thing is that both ISAPI Extensions work fine when they are configured as the only ISAPI extension in the system. We have problems only when both ISAPIs are used to process the same requests Regarding do***entation HSE_REQ_EXEC_URL can not be used with SSL. SSL (as well as compression) support is unfortunatelly a client requirement for me Jivk This can be accomplished by "Wildcard application mapping", which is a ISAPI Extension configured to trigger on "all extensions", examine/modif the incoming request, and then pass the modification along to be executed In your case, you can configure a wildcard application mapping at th Website level (and if you override the ScriptMap at child URLs/vdirs, yo must reconfigure the wildcard mapping at those levels as well), whic examines/modifies the incoming request and passes it along. Thus, when yo make a request directly to your other ISAPI Extension, this website-leve one will examine/modify the request first, and then pass it to your othe ISAPI Extension Please do the following - Read product do***entation as well as IIS Architectural do***entation o "Wildcard application mapping" and how to configure the - MSDN Do***entation on HSE_REQ_EXEC_UR - Look at Platform SDK for IIS and sample code using HSE_REQ_EXEC_UR - Google this newsgroup for the many questions, answers, and sample cod that have been posted regarding HSE_REQ_EXEC_UR http://www.microsoft.com/downloads/details.aspx?FamilyID=80a1b6e6-829e-49b7-8c02-333d9c148e69&DisplayLang=e http://www.microsoft.com/msdownload/platformsdk/sdkupdate/default.ht -- //Davi II This posting is provided "AS IS" with no warranties, and confers no rights / "Jivko" <anonymous@discussions.microsoft.com> wrote in messag news:64F353F3-154B-4CA1-8143-99C436671096@microsoft.com.. Hello I have the following problem I have and ISAPI extension that is directl accessible by Inet clients of my IIS6 I also need another ISAPI extension set on Web Site level that I would lik to process all requests including the ones that are sent to my main ISAP Extension What I see currently is that requests to my main Extension are receive unmodified so they are not passed tru the other ISAPI Extension (which work fine by its own) Is there any way I should set my IIS6 so requests to my main ISAPI are firs processed by my Web Site level ISAPI Any configuration tricks are welcome Jivk |
|
|
|
4
27th August 15:48
External User
Posts: 1
|
Multiple ISAPI extensions problem
Umm, where are you reading in do***entation that states that
HSE_REQ_EXEC_URL DOES NOT work with SSL and compression?? Please give a URL or reference. Based on your description, Wildcard Application Mapping using HSE_REQ_EXEC_URL should easily solve your problem. I can only say that it is possible to have multiple ISAPI Extensions processing the same request if you write the ISAPI Extensions correctly. If you have two ISAPI DLLs that do not work with each other, then you need to debug them both to figure out why. If you want assistance on debugging the ISAPI DLLs, then you will need to describe in greater detail how each is configured (exactly) as well as what ISAPI function calls are made, logically, by each ISAPI. -- //David IIS This posting is provided "AS IS" with no warranties, and confers no rights. // Hello David, The ISAPI that I have described as configured on Web Site level is defined as Wildcard Application Map. I do not know any other way to set an ISAPI Extension to process all requests on IIS 6. This works just fine by its own. The strange thing is that both ISAPI Extensions work fine when they are configured as the only ISAPI extension in the system. We have problems only when both ISAPIs are used to process the same requests. Regarding do***entation HSE_REQ_EXEC_URL can not be used with SSL. SSL (as well as compression) support is unfortunatelly a client requirement for me. Jivko ----- David Wang [Msft] wrote: ----- This can be accomplished by "Wildcard application mapping", which is an ISAPI Extension configured to trigger on "all extensions", examine/modify the incoming request, and then pass the modification along to be executed. In your case, you can configure a wildcard application mapping at the Website level (and if you override the ScriptMap at child URLs/vdirs, you must reconfigure the wildcard mapping at those levels as well), which examines/modifies the incoming request and passes it along. Thus, when you make a request directly to your other ISAPI Extension, this website-level one will examine/modify the request first, and then pass it to your other ISAPI Extension. Please do the following: - Read product do***entation as well as IIS Architectural do***entation on "Wildcard application mapping" and how to configure them - MSDN Do***entation on HSE_REQ_EXEC_URL - Look at Platform SDK for IIS and sample code using HSE_REQ_EXEC_URL - Google this newsgroup for the many questions, answers, and sample code that have been posted regarding HSE_REQ_EXEC_URL http://www.microsoft.com/downloads/details.aspx?FamilyID=80a1b6e6-829e-49b7-8c02-333d9c148e69&DisplayLang=en http://www.microsoft.com/msdownload/platformsdk/sdkupdate/default.htm -- //David IIS This posting is provided "AS IS" with no warranties, and confers no rights. // "Jivko" <anonymous@discussions.microsoft.com> wrote in message news:64F353F3-154B-4CA1-8143-99C436671096@microsoft.com... Hello, I have the following problem I have and ISAPI extension that is directly accessible by Inet clients of my IIS6. I also need another ISAPI extension set on Web Site level that I would like to process all requests including the ones that are sent to my main ISAPI Extension. What I see currently is that requests to my main Extension are received unmodified so they are not passed tru the other ISAPI Extension (which works fine by its own). Is there any way I should set my IIS6 so requests to my main ISAPI are first processed by my Web Site level ISAPI? Any configuration tricks are welcome. Jivko |
|
|
Linear Mode
