Manually install an SSL certificate on my IIS 7 server

Copy your certificate files onto the server

1. Find the directory on your server where certificate and key files are stored, then upload your intermediate certificate (gd_iis_intermediates.p7b or similar) and primary certificate (.crt file with randomized name) into that folder.

Add a Certificate Snap-in to the Microsoft Management Console (MMC)

1. Click on your Start Menu, then click Run.
2. In the prompt, type mmc and click OK.
3. Click File, then click Add/Remove Snap-in.
4. On the new window, click the Add button.
5. On the new window, select Certificates and click Add.
6. Select Computer account for the snap-in and click Next.
7. Click Local computer and click Finish.
8. Click Close on the Add Standalone Snap-in window.
9. Click OK on the Add/Remove Snap-in window.

Import the Intermediate SSL Certificate

1. In the MCC Console, click ▸ to expand Certificates (Local Computer).
2. Right click on the Intermediate Certification Authorities folder, hover over All Tasks and click Import.
3. On the new window, click Next.
4. Click Browse, find your previously uploaded intermediate certificate file and click Open.
5. Click Next, verify that the certificate information is proper and click Finish.
6. Close the the import was successful notification.

Install your SSL certificate

1. Click on your Start Menu, then click Run.
2. In the prompt, type inetmgr and click OK to launch the Internet Information Services (IIS) Manager.
3. Under the Connections panel on the left, click on your Server Name.
4. In the main panel under the IIS section, double click on Server Certificates.
5. Under the Actions panel on the right, click Complete Certificate Request.
6. On the new window, click ... to browse, find your previously uploaded primary certificate file and click Open.
7. Add a Friendly name to easily identify this certificate in the future.
8. Click OK.

Bind the SSL certificate

1. Under the Connections panel on the left, click ▸ to expand the Sites folder.
2. Click the Site Name that you plan to install the SSL certificate onto.
3. Under the Actions panel on the right, find the Edit Site section and click Bindings.
4. On the new window, click Add and fill out the following information:
   • Type: select https.
   • IP Address: select All Unassigned.
   • Port: type in 443.
   • Host name: leave this empty.
   • SSL Certificate: select your recently installed SSL.
5. Click OK to confirm, then Close for the Site Bindings window.

Restart IIS

1. Under the Actions panel on the right, find the Manage Website section and click Restart.

Difference between HTTP.SYS and WAS in IIS

HTTP.SYS (Hypertext Transfer Protocol Stack) is the kernel level components of IIS. All client request comes from client hit the HTTP.Sys of Kernel level. HTTP.SYS then makes a queue for each and every request for each and individual application pool based on the request.

Whenever we create any application pool IIS automatically registers the pool with HTTP.SYS to identify the particular during request processing.

WAS(Windows Activation Service) is a new feature of IIS, that allows all the features of the Windows Communication Framework stack, like non-HTTP channels and other stuff.

IIS is the web server that hosts the services that are activated via WAS.

WAS - is the new process activation mechanism that ships with IIS 7.0. WAS builds on the existing IIS 6.0 but is more powerful because it provides support for other protocols besides HTTP, such as TCP and Named Pipes.

For more details, go through IIS architecture

405 - HTTP verb used to access this page is not allowed

We get the above error when we use PUT verb when we access RESTFUL web services.

For this to work, The web site had to continue to enable WebDAV, but the web application needed to turn it off in order to support PUT and DELETE in its REST API.

Below are the approaches I followed to solve my problem.

Procedure 1:

1. In the IIS Manager, select the application that needs to support PUT.  
2. In the Features View, find WebDAV Authoring Rules.  Double-click it, or select Open Feature from the context menu (right-click).
3. In the Actions pane, find and click on WebDAV Settings....
4. In the WebDAV Settings, find Request Filtering Behavior, and under that, find Allow Verb Filtering.  Set Allow Verb Filtering to False.
5. In the Actions pane, click Apply.

Procedure 2:

1. Go to IIS Manager.
2. Click on your app.
3. Go to "Handler Mappings".
4. In the feature list, double click on "WebDAV".

5. Click on "Request Restrictions".
6. In the tab "Verbs" select "All verbs" .

7. Press OK.

Hope this helps!

How to add MIME types in Web.config on hosted Servers, Go Daddy, IIS 7 etc.

Ever wanted to add a custom mime type to your Web server?  I ran into this issue the other day when I tried to serve up .otf files related to fonts on my Web server and  I got this error: 404.3 error - mime type missing!

Thankfully, adding mime types is easier than ever thanks to the all-new distributed configuration option, which allows for IIS7 configuration to be stored in web.config files, along with asp.net configuration, to be deployed with your content. 

I'll show how easy it is to add mime types to your Web server.  This method will work on any IIS7 web server, and it will be ignored on all non-IIS7 web servers, so it should be safe to do no matter the type of application or content.  Since the <staticContent> section is delegated by default, the configuration snippets below should 'just work' on all IIS7 Web sites. 

1. Open or edit the web.config in your site home directory.
2. Add the following section in configuration section under web server.

<system.webServer>   
    <staticContent>
      <mimeMap fileExtension=".otf" mimeType="font/otf" />
    </staticContent>
</system.webServer>

This works even on Go Daddy hosted server also. You can add as many file times you want allow in this static content section.  For example these few MIME types you can add if you want on your Web server

<mimeMap fileExtension=".m4v" mimeType="video/m4v" />
<mimeMap fileExtension=".ogg" mimeType="audio/ogg" />
<mimeMap fileExtension=".oga" mimeType="audio/ogg" />
<mimeMap fileExtension=".ogv" mimeType="video/ogg" />
<mimeMap fileExtension=".webm" mimeType="video/webm"/>
<!-- For silverlight applicaitons -->
<mimeMap fileExtension=".xaml" mimeType="application/xaml+xml" />
<mimeMap fileExtension=".xap" mimeType="application/x-silverlight-app" />
<mimeMap fileExtension=".xbap" mimeType="application/x-ms-xbap" />

Hope this helps