<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://forums.iis.net/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:cs="http://blogs.iis.net/"><channel><title>Security</title><link>http://forums.iis.net/1031.aspx</link><description>A forum aimed at helping understand IIS security such as Authentication, IP restrictions, and SSL</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP1 (Build: 20510.895)</generator><item><title>Re: Securing sites - classic asp - .Net 1.1, .Net 2.0, and .Net 3+</title><link>http://forums.iis.net/thread/1882044.aspx</link><pubDate>Wed, 15 Oct 2008 01:37:31 GMT</pubDate><guid isPermaLink="false">50bcf3b4-f6fe-4638-adff-0c150e922e99:1882044</guid><dc:creator>naziml</dc:creator><slash:comments>0</slash:comments><comments>http://forums.iis.net/thread/1882044.aspx</comments><wfw:commentRss>http://forums.iis.net/commentrss.aspx?SectionID=1031&amp;PostID=1882044</wfw:commentRss><description>&lt;p&gt;You can use IIS config to redirect instead of the application doing it. Here&amp;#39;s how you set this up for IIS6: &lt;a href="http://technet.microsoft.com/en-us/library/cc736641.aspx"&gt;http://technet.microsoft.com/en-us/library/cc736641.aspx&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Re: Securing sites - classic asp - .Net 1.1, .Net 2.0, and .Net 3+</title><link>http://forums.iis.net/thread/1882022.aspx</link><pubDate>Tue, 14 Oct 2008 17:20:57 GMT</pubDate><guid isPermaLink="false">50bcf3b4-f6fe-4638-adff-0c150e922e99:1882022</guid><dc:creator>mybestguess</dc:creator><slash:comments>0</slash:comments><comments>http://forums.iis.net/thread/1882022.aspx</comments><wfw:commentRss>http://forums.iis.net/commentrss.aspx?SectionID=1031&amp;PostID=1882022</wfw:commentRss><description>&lt;p&gt;Thank you. I know about the certificates but I didn&amp;#39;t know if there was an easier solution.&amp;nbsp; We have 7 certificates for 7 domains and on 3 of those domains, there are 20+ sites that need to have SSL enabled.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;The only problem I saw with that is there will be a lot of custom code entered to handle redirects to https and I didn&amp;#39;t know if there was an easier way to handle the redirect instead of custom coding each of the 75+ sites?&lt;/p&gt;</description></item><item><title>Re: Securing sites - classic asp - .Net 1.1, .Net 2.0, and .Net 3+</title><link>http://forums.iis.net/thread/1881974.aspx</link><pubDate>Tue, 14 Oct 2008 11:07:08 GMT</pubDate><guid isPermaLink="false">50bcf3b4-f6fe-4638-adff-0c150e922e99:1881974</guid><dc:creator>jeff@zina.com</dc:creator><slash:comments>0</slash:comments><comments>http://forums.iis.net/thread/1881974.aspx</comments><wfw:commentRss>http://forums.iis.net/commentrss.aspx?SectionID=1031&amp;PostID=1881974</wfw:commentRss><description>&lt;p&gt;&lt;BLOCKQUOTE&gt;&lt;div&gt;&lt;img src="/Themes/iis/images/icon-quote.gif"&gt; &lt;strong&gt;mybestguess:&lt;/strong&gt;&lt;/div&gt;&lt;div&gt;If you have any suggestions regarding the best way to add SSL to existing sites please let me know.&amp;nbsp;&lt;/div&gt;&lt;/BLOCKQUOTE&gt;&lt;/p&gt;
&lt;p&gt;Install the certificate and check the Require Secure Connections box.&lt;/p&gt;
&lt;p&gt;Jeff&lt;/p&gt;</description></item><item><title>Securing sites - classic asp - .Net 1.1, .Net 2.0, and .Net 3+</title><link>http://forums.iis.net/thread/1881921.aspx</link><pubDate>Mon, 13 Oct 2008 18:54:58 GMT</pubDate><guid isPermaLink="false">50bcf3b4-f6fe-4638-adff-0c150e922e99:1881921</guid><dc:creator>mybestguess</dc:creator><slash:comments>0</slash:comments><comments>http://forums.iis.net/thread/1881921.aspx</comments><wfw:commentRss>http://forums.iis.net/commentrss.aspx?SectionID=1031&amp;PostID=1881921</wfw:commentRss><description>&lt;p&gt;It as been the recent task of our team to come up with both short and long term solutions to the concern of SSL security on our sites.&lt;/p&gt;
&lt;p&gt;The first solution off the top of the head is to do 1 of the following 2.&amp;nbsp; Either take the pain and time consuming option of coding each individual website to rediret to https to use ssl.&amp;nbsp; The second approach would be to have IIS force a redirect to the https and www paths.&lt;/p&gt;
&lt;p&gt;The catch is what would be the best approach.&amp;nbsp; I am thinking of a quick and easy temporary solution first.&amp;nbsp; Then a long term solution.&amp;nbsp; But the long term solution has a catch.&amp;nbsp; In the next few months (early - Mid 2009) we are moving to Server 2008 with IIS7 and that may negate the changes necessary in IIS6.&lt;/p&gt;
&lt;p&gt;Any and all suggestions are appreciated on this matter.&amp;nbsp; If you have any suggestions regarding the best way to add SSL to existing sites please let me know.&amp;nbsp; I would like to try and avoid a manual reprogramming of that many websites.&amp;nbsp; Thank you&lt;/p&gt;
&lt;p&gt;MBG&lt;/p&gt;</description></item></channel></rss>