<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Pressing the Red Button &#187; IIS</title>
	<atom:link href="http://www.pressthered.com/tag/iis/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pressthered.com</link>
	<description>Adventures in Software Development</description>
	<lastBuildDate>Sun, 05 Sep 2010 16:55:12 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Rejected-By-UrlScan 404 Errors</title>
		<link>http://www.pressthered.com/rejected-by-urlscan_404_errors/</link>
		<comments>http://www.pressthered.com/rejected-by-urlscan_404_errors/#comments</comments>
		<pubDate>Sat, 04 Jul 2009 05:59:56 +0000</pubDate>
		<dc:creator>jim.richmond</dc:creator>
				<category><![CDATA[Tech Tips]]></category>
		<category><![CDATA[.Net]]></category>
		<category><![CDATA[IIS]]></category>

		<guid isPermaLink="false">http://www.pressthered.com/?p=446</guid>
		<description><![CDATA[If you are getting some unexplainable 404 errors when accessing html or asp.net pages in IIS, and have exhausted the more common issues, check out your log file for URLScan errors. URLScan is a Microsoft security tool to help protect Internet Information Server. On your developer environment it might be getting in the way.

How Can [...]]]></description>
			<content:encoded><![CDATA[<p>If you are getting some unexplainable 404 errors when accessing html or asp.net pages in IIS, and have exhausted the more common issues, check out your log file for URLScan errors. <a href="technet.microsoft.com/en-us/security/cc242650.aspx">URLScan</a> is a Microsoft security tool to help protect Internet Information Server. On your developer environment it might be getting in the way.</p>
<ol>
<strong>How Can I Disable URLScan</strong></p>
<li>Go to the Control Panel -> Administrative Tools -> Internet Information Services </li>
<li>Click WebSites folder, right click to get Properties</li>
<li>Click ISAPI Filters tab, find URLScan in the list, click Remove button, then OK to save</li>
<li>From Command Prompt (Start -> Run -> Cmd), type &#8220;iisreset&#8221;, to restart IIS</li>
</ol>
<p><strong>How Do I Configure URL Scan</strong><br />
<em>There is a configuration file located here:<br />
&lt;Windows Folder&gt;\system32\inetsrv\urlscan\UrlScan.ini</em><br />
Additional log files are also stored in that directory.<br />
If you want to keep URLScan on your computer, you can check out <a href="http://msdn.microsoft.com/en-us/library/aa302368.aspx">Microsoft&#8217;s documentation</a>.</p>
<p><strong>How Did It Get Installed</strong><br />
I have no idea in my case. I didn&#8217;t bother to look into it further. I am guessing through some Windows Update or some unintentionally clicking.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.pressthered.com/rejected-by-urlscan_404_errors/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Redirecting Your Domain Using 301 Redirects</title>
		<link>http://www.pressthered.com/redirecting_your_domain_using_301_redirects/</link>
		<comments>http://www.pressthered.com/redirecting_your_domain_using_301_redirects/#comments</comments>
		<pubDate>Wed, 17 Jun 2009 06:14:45 +0000</pubDate>
		<dc:creator>jim.richmond</dc:creator>
				<category><![CDATA[Tech Tips]]></category>
		<category><![CDATA[301 Redirect]]></category>
		<category><![CDATA[apache]]></category>
		<category><![CDATA[htaccess]]></category>
		<category><![CDATA[IIS]]></category>
		<category><![CDATA[seo]]></category>

		<guid isPermaLink="false">http://www.pressthered.com/?p=232</guid>
		<description><![CDATA[What are 301 redirects?
It is the status code that has been sent back to your browser from the web server. In other words, the &#8220;301 status&#8221;, is telling your browser that the link you typed in or clicked on has moved permanently to the new address that you have just been forwarded to.
When would I [...]]]></description>
			<content:encoded><![CDATA[<p><strong>What are 301 redirects?</strong><br />
It is the status code that has been sent back to your browser from the web server. In other words, the &#8220;301 status&#8221;, is telling your browser that the link you typed in or clicked on has moved permanently to the new address that you have just been forwarded to.</p>
<p><strong>When would I use a 301 Redirect?</strong><br />
One reason is to redirect your current domain name to a new domain name. If you changed your domain name for example. It could also be used for redirecting individual pages if a page has moved and you want to redirect old links to a new page. Today we just talk about updating your site to use a new domain name.</p>
<ol>
<strong>How do I redirect my old domain name to a new domain in Linux/Unix</strong></p>
<li>Ideally you should make a copy of your existing site. Either on a new hosting account or as a new domain on your existing account (if your host allows it). When both sites (old and new) are set up and working individually with their own domain names, you can proceed to redirect your old domain name to your new domain name.</li>
<li>Create a .htaccess file in the root directory of your old website. You can also create the file on your own computer first than ftp it in. If using Windows, you could name it &#8220;htaccess&#8221; then rename it &#8220;.htaccess&#8221; from your ftp program after you upload.</li>
<li>Copy and paste this code into that file, changing the &#8220;www.yourdomain.com&#8221; text to <strong>your</strong> new domain name:<br />
<strong>Options +FollowSymLinks<br />
RewriteEngine on<br />
RewriteRule ^(.*)$ http://www.yourdomain.com/$1 [R=301,L]</strong>
</li>
<li>That is all there is to it, it immediately goes into effect. You can test it by opening a new browser and typing in any link to your old site. It should redirect to the same page on your new site. If it does not, check to ensure that you added a period in front of the .htaccess file</li>
</ol>
<p><strong>How do I redirect my old domain name to a new domain in IIS (Internet Information Server) on Windows?</strong><br />
You will probably need to talk to your host to determine the best method. If you have admin access to your server you can do this:</p>
<ol>
<li> Right click the folder or website you want to redirect and click Properties.</li>
<li> On the Home Directory (or Virtual Directory) tab, click the &#8220;A redirection to a URL&#8221; option.</li>
<li> Enter the domain name or page you want to redirect to.</li>
<li> Check the &#8220;A permanent redirection for this resource&#8221; option.</li>
<li> Save by clicking OK. Then test by opening a new browser and going to an old link. It should redirect to the new domain.</li>
</ol>
<div id="attachment_238" class="wp-caption aligncenter" style="width: 310px"><img src="http://www.pressthered.com/wp-content/uploads/2009/06/redirect1-300x294.gif" alt="Redirecting a Domain Name in IIS" title="Redirecting a Domain Name in IIS" width="300" height="294" class="size-medium wp-image-238" /><p class="wp-caption-text">Redirecting a Domain Name in IIS</p></div>
<p><strong>Additional Resources:</strong><br />
<a href="http://googlewebmastercentral.blogspot.com/2008/04/best-practices-when-moving-your-site.html">Google recommends</a> using 301 redirects if changing the domain name of your existing site to get the best results in their index.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.pressthered.com/redirecting_your_domain_using_301_redirects/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Slow Web Service calls to LocalHost in ASP.NET</title>
		<link>http://www.pressthered.com/slow_web_service_calls_to_localhost_in_aspnet/</link>
		<comments>http://www.pressthered.com/slow_web_service_calls_to_localhost_in_aspnet/#comments</comments>
		<pubDate>Wed, 05 Nov 2008 06:13:37 +0000</pubDate>
		<dc:creator>jim.richmond</dc:creator>
				<category><![CDATA[Tech Tips]]></category>
		<category><![CDATA[ASP.Net]]></category>
		<category><![CDATA[IIS]]></category>
		<category><![CDATA[web services]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://www.pressingtheredbutton.com/?p=43</guid>
		<description><![CDATA[Here&#8217;s a few troubleshooting steps you can use to resolve slow calls to web services that are on your local host.
1. When I googled this issue, I found this link. It reveals a setting you can make in your web.config to force all calls to local web services to bypass your proxy (if you have [...]]]></description>
			<content:encoded><![CDATA[<p>Here&#8217;s a few troubleshooting steps you can use to resolve slow calls to web services that are on your local host.</p>
<p>1. When I googled this issue, I found <a href="http://www.west-wind.com/WebLog/posts/3871.aspx">this link</a>. It reveals a setting you can make in your web.config to force all calls to local web services to bypass your proxy (if you have one). While I did have an internet proxy server, my local calls were not using it. You can validate this by first checking that your web service instance is using a proxy and your .asmx address is set to bypass the proxy (using <a href="http://msdn.microsoft.com/en-us/library/system.net.webproxy.isbypassed.aspx">WebProxy.IsBypassed</a>).</p>
<p>2. What ended up being my problem is that I had Windows Authentication set on my web service virtual directory. This isn&#8217;t the default but it got set at some point. The problem was that the first call to the web service got an access denied error (401) and the second call would go through fine (I assume by trying default credentials). So the delay was in the 401 error. One error isn&#8217;t really noticeable, but string together 5 or 10 calls on one page and the delay is unbearable. For reference, the log files revealed the 401 errors and the multiple calls.</p>
<p>If you want to go a step further (and you are bored), you can <a href="http://support.microsoft.com/kb/907273">troubleshoot the 401 errors</a> in your iis log files.</p>
<p>Hope this helps.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.pressthered.com/slow_web_service_calls_to_localhost_in_aspnet/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
