Internet Server Application Programming Interface: Difference between revisions

Revision as of 09:54, 11 June 2010

Latest revision as of 14:04, 24 March 2025

(53 intermediate revisions by 45 users not shown)

Line 1:

The '''Internet Server Application Programming Interface''' ('''ISAPI''') is an [[N''n''-tier]] [[Application programming interface|API]] of [[Internet Information Services]] (IIS), [[Microsoft]]'s collection of [[Microsoft Windows|Windows]]-based web server services. The most prominent application of IIS and ISAPI is Microsoft's [[web server]].

The ISAPI has also been implemented by [[Apache HTTP Server|Apache]]'s <tt>{{mono|mod_isapi</tt>}} module so that server-side web applications written for Microsoft's IIS can be used with Apache,. and otherOther third-party web servers like [[Zeus Web Server]] offer ISAPI interfaces, too.

[[Image:IIS ISAPI Filters.jpg|thumb|ISAPI Filters dialog in Microsoft IIS]]

The word "server" can refer to a computer ("box") or a piece of software (for example, ''SQL Server''). [[Microsoft]]'s web server application software is called [[Internet Information Services]], which is made up of a number of "sub-applications" and is very configurable. [[ASP.NET]] is one such slice of IIS, allowing a programmer to write web applications in his or hertheir choice of programming language (VB.NET, C#, JF#) that's supported by the Microsoft .NET [[Common Language Runtime|CLR]]. '''ISAPI''' is a much lower-level programming system, giving much better performance, at the expense of simplicity. While Microsoft is generally credited with the creation of the ISAPI specification, it was actually co-developed by Process Software and Microsoft with input from a small number of other vendors.<ref>[http://wasd.vsm.com.au/ht_root/doc/scripting/scripting_0600.html ISAPI<!-- Bot generated title -->]</ref>

The ISAPI has also been implemented by [[Apache HTTP Server|Apache]]'s <tt>mod_isapi</tt> module so that server-side web applications written for Microsoft's IIS can be used with Apache, and other third-party web servers like [[Zeus Web Server]] offer ISAPI interfaces.

==Big Picture==

The word "server" can refer to a computer ("box") or a piece of software (for example, ''SQL Server''). [[Microsoft]]'s web server application software is called [[Internet Information Services]], which is made up of a number of "sub-applications" and is very configurable. [[ASP.NET]] is one such slice of IIS, allowing a programmer to write web applications in his or her choice of programming language (VB.NET, C#, J#) that's supported by the Microsoft .NET [[Common Language Runtime|CLR]]. '''ISAPI''' is a much lower-level programming system, giving much better performance, at the expense of simplicity. While Microsoft is generally credited with the creation of the ISAPI specification, it was actually co-developed by Process Software and Microsoft with input from a small number of other vendors.<ref>[http://wasd.vsm.com.au/ht_root/doc/scripting/scripting_0600.html ISAPI<!-- Bot generated title -->]</ref>

==Performance and compromise==

The greatest disadvantage of developing web applications at ISAPI level is the increased development time over typical scripting languages like PHP and ASP. Another penalty is the lack of native support for many standard web application features such as [[session (computer science)|session]] handling, which are common features in technologies such as ASP and PHP. Because ISAPI extensions are normally written in unmanaged languages like C, there is an increased risk of [[buffer overflows]] and similar vulnerabilities occurring unless explicitly accounted for.

ISAPI filters and extensions do offer the greatest possible performance for web applications due in part to their use of native code as well their tight integration with the actual webserver. ISAPI filters in particular allow for low-level interaction with HTTP messages that are not available via any other mechanism. Due to these performance advantages many scripted languages such as PHP have versions of their interpreters available in ISAPI form.

===ISAPI for IIS 5.0 and earlier===

In contrast to [[Common Gateway Interface|CGI]] applications, an ISAPI application is loaded into the same process space as the IIS web server. This removes the need for inter-[[Process (computing)|process]] calls and the overhead of loading and starting a separate executable, allowing improved performance of ISAPI applications over CGI applications. However, if an ISAPI application [[Crash (computing)|crashes]], it can cause the whole of the web server to crash along with it.

===ISAPI for IIS 6.0===

In IIS 6.0 it is possible to configure an IIS application to run in a separate process space created by IIS (recommended mode: "High (isolated)"). Thus, performance is maintained but if the ISAPI application crashes it will not cause the whole IIS server to crash.

==ISAPI applications==

ISAPI consists of two components: Extensions and Filters.<ref>{{Cite book |title=Web commerce security : design and development|last=Hadi.|first=Nahari|date=2011|publisher=Wiley Pub|others=Krutz, Ronald L.|isbn=9781118098899|___location=Indianapolis|pages=157|oclc=757394142}}</ref> These are the only two types of applications that can be developed using ISAPI. Both Filters and Extensions must be compiled into DLL files which are then registered with IIS to be run on the web server.

ISAPI applications can be written using any language which allows the export of standard C functions, for instance C, C++, Delphi. There are a couple of libraries available which help to ease the development of ISAPI applications, and in Delphi Pascal the Intraweb components for web-application development. [[Microsoft Foundation Class Library|MFC]] includes classes for developing ISAPI applications. Additionally, there is the [[ATL Server]] technology which includes a C++ library dedicated to developing ISAPI applications.

===Extensions===

ISAPI Extensions are true applications that run on IIS. They have access to all of the functionality provided by IIS. ISAPI extensions are implemented as [[DLLDynamic-link library|DLLs]] that are loaded into a process that is controlled by IIS. Clients can access ISAPI extensions in the same way they access a static HTML page. Certain file extensions or a complete folder or site can be mapped to be handled by an ISAPI extension.

===Filters===

ISAPI filters are used to modify or enhance the functionality provided by IIS. They always run on an IIS server and filter every request until they find one they need to process. Filters can be programmed to examine and modify both incoming and outgoing streams of data. Internally programmed and externally configured priorities determine in which order filters are called.

Filters are implemented as DLL filesDLLs and can be registered on an IIS server on a site level or a global level (i.e., they apply to all sites on an IIS server). Filters are initialised when the worker process is started and listens to all requests to the site on which it is installed.

Common tasks performed by ISAPI filters include:

*Changing request data (URLs or headers) sent by the client

*Controlling which physical file gets mapped to the URL

*Controlling the user name and password used with anonymous or [[Basic access authentication|basic authentication]]

*Modifying or analyzing a request after authentication is complete

*Modifying a response going back to the client

Line 41 ⟶ 27:

*Running processing when a request is complete

*Run processing when a connection with the client is closed

*Performing special logging or [[Web analytics|traffic analysis]].

*Performing custom authentication.

*Handling encryption and compression.

Line 48 ⟶ 34:

This is a list of common ISAPI applications implemented as ISAPI extensions:

* [[Active Server Pages]] (ASP), installed as standard

* ActiveVFP, Active Visual FoxPro installed on IIS

* [[ASP.NET]], installed as standard on IIS 6.0 onwards

* [[Adobe ColdFusion|ColdFusion]], later versions of ColdFusion are installable on IIS

* [[Perl]] ISAPI (aka Perliis), available for free to install

* [[PHP]], available for free to install, not maintained anymore.<ref>{{Cite web|url=https://bugs.php.net/bug.php?id=48299|title = PHP :: Bug #48299 :: Missing php5isapi.DLL in package}}</ref>

==ISAPI Developmentdevelopment==

ISAPI applications can be developed using any development tool that can generate a Win32[[Windows API|Windows]] DLL. Wizards for generating ISAPI framework applications have been available in Microsoft development tools since Visual C++ 4.0.

==See also==

*[[Internet Information Services]]

*[[ATL Server]]

*[[Server Applicationapplication Programmingprogramming Interfaceinterface|SAPI]]

*[[C++]]

*[[PHP]]

*[[FastCGI]]

{{Web server interfaces}}

==Footnotes==

<references/>

==References==

{{Reflist}}

==External links==

*[http://www.genusa.com/isapi/ The ISAPI Developer's site]

{{Web server interfaces}}

[[Category:Microsoft application programming interfaces]]

[[ca:ISAPI]]

[[de:Internet Server API]]

[[es:ISAPI]]

[[fr:ISAPI]]

[[it:ISAPI]]

[[he:Internet Server API]]

[[mn:ISAPI]]

[[ja:ISAPI]]

[[pt:ISAPI]]

[[ru:ISAPI]]

[[uk:ISAPI]]