<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>IIS Express on JaBoet</title>
    <link>https://blog.wernerpeenz.com/tags/iis-express/</link>
    <description>Recent content in IIS Express on JaBoet</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <managingEditor>wpeenz@outlook.com (Werner Peenz)</managingEditor>
    <webMaster>wpeenz@outlook.com (Werner Peenz)</webMaster>
    <lastBuildDate>Mon, 24 Feb 2020 05:15:06 +0000</lastBuildDate><atom:link href="https://blog.wernerpeenz.com/tags/iis-express/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Replacing IIS Express self signed certificate</title>
      <link>https://blog.wernerpeenz.com/post/replacing-iis-express-certificate/</link>
      <pubDate>Mon, 24 Feb 2020 05:15:06 +0000</pubDate>
      <author>wpeenz@outlook.com (Werner Peenz)</author>
      <guid>https://blog.wernerpeenz.com/post/replacing-iis-express-certificate/</guid>
      <description>Firefox does not allow sites with self signed certificates, which is the case when using IIS Express. Best solution I&amp;rsquo;ve found thus far is go generate a certificate as per Installing a localhost certificate (for use in IIS), then replacing the IIS Express certificate using the answer to the Stackoverflow question at How do I change my IIS Express SSL certificate for one that will work with Chrome 58+?
Works a treat (and means that I&amp;rsquo;m using the same localhost cert across front end (Aurelia), legacy WCF service and a ASP.</description>
    </item>
    
  </channel>
</rss>
