<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>IIS on Brian Beach</title>
    <link>http://blog.brianbeach.com/tags/iis/</link>
    <description>Recent content in IIS on Brian Beach</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 04 Dec 2011 13:04:00 -0500</lastBuildDate><atom:link href="http://blog.brianbeach.com/tags/iis/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>SSL, IIS, and Host Headers</title>
      <link>http://blog.brianbeach.com/2011/12/ssl-iis-and-host-headers.html</link>
      <pubDate>Sun, 04 Dec 2011 13:04:00 -0500</pubDate>
      
      <guid>http://blog.brianbeach.com/2011/12/ssl-iis-and-host-headers.html</guid>
      <description>There is a lot of confusion about how IIS handles SSL. With all the confusion out there, I thought I should put together a quick post. This post will also explain the error message: At least one other site is using the same HTTPS binding and the binding is configured with a different certificate.
My discussions this week were specific to SharePoint, but the confusion is with host headers in IIS.</description>
    </item>
    
    <item>
      <title>Binding not Created for Host Header Site Collections</title>
      <link>http://blog.brianbeach.com/2010/12/binding-not-created-for-host-header.html</link>
      <pubDate>Sat, 25 Sep 2010 08:00:00 -0400</pubDate>
      
      <guid>http://blog.brianbeach.com/2010/12/binding-not-created-for-host-header.html</guid>
      <description>I noticed what I think is a bug (or maybe a limitation) in SharePoint 2010. When I use PowerShell to create a Host Header Site Collection, SharePoint does not create a binding in IIS. If I add the binding manually, everything works great, but I would expect SharePoint to do this for. Am I missing something?
The following PowerShell script will create a new web application. Note that I have the option to add a host header.</description>
    </item>
    
  </channel>
</rss>
