Hi All, I have an ISAPI filter + extension (.dll) written for IIS 6 webserver. It supports following callbacks: SF_NOTIFY_SEND_RAW_DATA SF_NOTIFY_END_OF_REQUEST SF_NOTIFY_PREPROC_HEADERS SF_NOTIFY_END_OF_NET_SESSION HttpExtensionProc ( supports wild card extension ) One of our customer are asking us to put our webserver filter + extension on Microsoft ISA based proxy server - 2006 version because they want to route all of the web requests to it. Can anyone please help me to understand if there would be any changes required to install and run our filters on Microsoft ISA Proxy Server? Can the ISAPI filters and extensions written for IIS6 be easily run on ISA based proxy server as well without modifying the application? Any help on this would be highly appreciated. Thanks barkha
On Sep 12, 11:20 pm, rupa wrote: > Hi All, > > I have an ISAPI filter + extension (.dll) written for IIS 6 webserver. > It supports following callbacks: > SF_NOTIFY_SEND_RAW_DATA > SF_NOTIFY_END_OF_REQUEST > SF_NOTIFY_PREPROC_HEADERS > SF_NOTIFY_END_OF_NET_SESSION > HttpExtensionProc ( supports wild card extension ) > > One of our customer are asking us to put our webserver filter + > extension on Microsoft ISA based proxy server - 2006 version because > they want to route all of the web requests to it. > > Can anyone please help me to understand if there would be any changes > required to install and run our filters on Microsoft ISA Proxy Server? > Can the ISAPI filters and extensions written for IIS6 be easily run on > ISA based proxy server as well without modifying the application? > > Any help on this would be highly appreciated. > > Thanks > barkha You will have to try and see what happens. Neither IIS6 team nor ISA 2006 team worked together to ensure the ISAPI Filter API are compatible with each other. But, they look very similar. People have reported success running the URLScan ISAPI Filter on both IIS and ISA, which listens on three of those four filter events. HttpExtensionProc has no analog on ISA Server since ISA Server is not an application endpoint. Depending on what you are doing in there, you may have to change code to get similar effect. //David http://w3-4u.blogspot.com http://blogs.msdn.com/David.Wang //
On Sep 12, 11:48 pm, David Wang wrote: > On Sep 12, 11:20 pm, rupa wrote: > > > > > Hi All, > > > I have an ISAPI filter + extension (.dll) written for IIS 6 webserver. > > It supports following callbacks: > > SF_NOTIFY_SEND_RAW_DATA > > SF_NOTIFY_END_OF_REQUEST > > SF_NOTIFY_PREPROC_HEADERS > > SF_NOTIFY_END_OF_NET_SESSION > > HttpExtensionProc ( supports wild card extension ) > > > One of our customer are asking us to put our webserver filter + > > extension on Microsoft ISA based proxy server - 2006 version because > > they want to route all of the web requests to it. > > > Can anyone please help me to understand if there would be any changes > > required to install and run our filters on Microsoft ISA Proxy Server? > > Can the ISAPI filters and extensions written for IIS6 be easily run on > > ISA based proxy server as well without modifying the application? > > > Any help on this would be highly appreciated. > > > Thanks > > barkha > > You will have to try and see what happens. > > Neither IIS6 team nor ISA 2006 team worked together to ensure the > ISAPI Filter API are compatible with each other. But, they look very > similar. People have reported success running the URLScan ISAPI Filter > on both IIS and ISA, which listens on three of those four filter > events. > > HttpExtensionProc has no analog on ISA Server since ISA Server is not > an application endpoint. Depending on what you are doing in there, you > may have to change code to get similar effect. > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang > // Thanks David so much for a quick reply. This information is really helpful.
