IIS6.0 UI vs. IIS 7.x UI Series: More about Web Service Extensions

Posted: Feb 05, 2010  3 comments  

Average Rating

Share this Post

This week in the blog series (Introduction to the series – here), let’s talk about Web Service Extensions feature in IIS6 UI and compare it to the IIS7.x ISAPI and CGI Restrictions feature.

Web Service Extensions feature in IIS6.0

By default, the IIS6.0 server only serves static content. Features like asp, asp.net, server side includes, webdav, front page server extensions would not work unless explicitly enabled. You can configure these features (also known as Web Service Extensions) using the Web Service Extensions node in the inetmgr tree view.

IIS6 UI – Web Service Extensions

WebServiceExtensions

To enable, disable a web service extension, you would

- Launch IIS Manager (run inetmgr)

- Select and expand the local computer node in the tree view

- Select  “Web Service Extensions” node in the tree view

- You can now “Allow” or “Prohibit” any Web Service Extension.

This UI also lets you Add a new Web Service extension, allow all web service extensions for a specific application and disable (“prohibit”) all web service extensions.

ISAPI and CGI Restrictions feature in IIS 7.0

In IIS7/7.5 UI, the web service extensions made it as a feature on the Server Home Page. Select the local server node; double click on the ISAPI and CGI restrictions feature from the Server Home Page

Isapi_CGI_Restrictions_HomePage

IIS7 UI – ISAPI and CGI Restrictions

Isapi_CGI_Restrictions

If you would like to add handler mappings to support ISAPI extensions or CGI programs, you would allow a specific CGI program (executable) or ISAPI extension (dll) by adding it to the ISAPI CGI Restrictions list. This feature determines the execution of 3 party ISAPI / CGI code.

To allow or restrict an ISAPI extension or CGI module, you would

- Launch IIS Manager (run inetmgr)

- Select and expand the local computer node in the tree view

- Select  “ISAPI and CGI Restrictions” feature from the Server Home Page

- You can now “Allow” or “Deny” any ISAPI extension or CGI module.

This UI also lets you Add /Edit or Remove an ISAPI or CGI Restriction. This UI also lets you allow/deny of all unknown CGI and ISAPI extensions by selecting the “Edit Feature Settings…” task in the Actions pane.

 

Next blog in the series: Anonymous Authentication

As always, please drop a comment if there are any specific UI modules/properties you would like to be compared next and also if you have any feedback on the level of detail.

Comments

You cannot download IIS, its released with Windows.

IIS6.0 was released with Windows 2003

IIS7.x was released with Windows Vista SP1,  Windows Server 2008 , Windows 7

Feb 08 2010 by NitashaV

When you google you will get a URL :www.microsoft.com/.../details.aspx

This url link is for IIS6.0 Resource kit, not IIS 6.0 server, you can only get IIS6.0 with Windows Server 2003, it's part of OS, no separate downloads.  Aggred with Nitasha.

Nammi

Dec 14 2010 by Nammi

First i thank you for your help,

I checked everything accordng to your descrptions but my site still cant access the web service. (Everything is ok in our iis6 server) Both are running currently -same application,db etc. - Just iis6.0 one can use webservice:S

What can i do to fix it? Thank you again

Feb 25 2011 by arkhon13