<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Case Sensitivity in URLs</title>
	<atom:link href="http://www.bin-co.com/blog/2007/10/case-sensitivity-in-urls/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bin-co.com/blog/2007/10/case-sensitivity-in-urls/</link>
	<description>Learn about the latest in Web Development - as soon as I do.</description>
	<lastBuildDate>Thu, 11 Mar 2010 15:19:14 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Amit Agarwal</title>
		<link>http://www.bin-co.com/blog/2007/10/case-sensitivity-in-urls/comment-page-1/#comment-1086</link>
		<dc:creator>Amit Agarwal</dc:creator>
		<pubDate>Sun, 14 Dec 2008 04:19:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.bin-co.com/blog/2007/10/case-sensitivity-in-urls/#comment-1086</guid>
		<description>I actually like the case-sensitivity part of the apache. I can have files with same name and still have different contents just with mix and match of characters.

But there&#039;s a way you can avoid that if you want to... just put your htdocs directory in the fat partition and you have same Apache setup with case insensitive working.</description>
		<content:encoded><![CDATA[<p>I actually like the case-sensitivity part of the apache. I can have files with same name and still have different contents just with mix and match of characters.</p>
<p>But there&#8217;s a way you can avoid that if you want to&#8230; just put your htdocs directory in the fat partition and you have same Apache setup with case insensitive working.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: William Loughborough</title>
		<link>http://www.bin-co.com/blog/2007/10/case-sensitivity-in-urls/comment-page-1/#comment-733</link>
		<dc:creator>William Loughborough</dc:creator>
		<pubDate>Wed, 15 Oct 2008 01:25:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.bin-co.com/blog/2007/10/case-sensitivity-in-urls/#comment-733</guid>
		<description>A related &quot;glitch&quot; for those of us who are at all lazy is the requirement (or lack of it) fot the &quot;www&quot; prefix.

E.g. http://ski.org doesn&#039;t work but http://www.ski.org does!

Some browsers might not like address bar entries without &quot;http://&quot; ??

Love.</description>
		<content:encoded><![CDATA[<p>A related &#8220;glitch&#8221; for those of us who are at all lazy is the requirement (or lack of it) fot the &#8220;www&#8221; prefix.</p>
<p>E.g. <a href="http://ski.org" rel="nofollow">http://ski.org</a> doesn&#8217;t work but <a href="http://www.ski.org" rel="nofollow">http://www.ski.org</a> does!</p>
<p>Some browsers might not like address bar entries without &#8220;http://&#8221; ??</p>
<p>Love.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Who&#8217;s idea was it to remove file extensions from URLs? :: Jaisen Mathai</title>
		<link>http://www.bin-co.com/blog/2007/10/case-sensitivity-in-urls/comment-page-1/#comment-674</link>
		<dc:creator>Who&#8217;s idea was it to remove file extensions from URLs? :: Jaisen Mathai</dc:creator>
		<pubDate>Sun, 13 Jul 2008 22:44:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.bin-co.com/blog/2007/10/case-sensitivity-in-urls/#comment-674</guid>
		<description>[...] http://www.bin-co.com/blog/2007/10/case-sensitivity-in-urls/ [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://www.bin-co.com/blog/2007/10/case-sensitivity-in-urls/" rel="nofollow">http://www.bin-co.com/blog/2007/10/case-sensitivity-in-urls/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George</title>
		<link>http://www.bin-co.com/blog/2007/10/case-sensitivity-in-urls/comment-page-1/#comment-268</link>
		<dc:creator>George</dc:creator>
		<pubDate>Sun, 30 Dec 2007 00:56:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.bin-co.com/blog/2007/10/case-sensitivity-in-urls/#comment-268</guid>
		<description>As suggested by m.kanlic, the RFCs on require only the scheme and host parts of the URL/URI to be case insensitive.

Note that making URLs case-insensitive reduces the effective namespace of your website, promotes laziness on the part of developers, and can result in unintentional and undesirable duplicate content issues.

Furthermore and regarding the comment on Apache using the filesystem as an excuse, note that the case -&gt; no-case transformation is uni-directional (i.e. cannot be reversed), which makes it practically impossible for Apache (or anything else) to use a case-sensitive filesystem with case-insensitive URLs.</description>
		<content:encoded><![CDATA[<p>As suggested by m.kanlic, the RFCs on require only the scheme and host parts of the URL/URI to be case insensitive.</p>
<p>Note that making URLs case-insensitive reduces the effective namespace of your website, promotes laziness on the part of developers, and can result in unintentional and undesirable duplicate content issues.</p>
<p>Furthermore and regarding the comment on Apache using the filesystem as an excuse, note that the case -&gt; no-case transformation is uni-directional (i.e. cannot be reversed), which makes it practically impossible for Apache (or anything else) to use a case-sensitive filesystem with case-insensitive URLs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: m.kanlic</title>
		<link>http://www.bin-co.com/blog/2007/10/case-sensitivity-in-urls/comment-page-1/#comment-219</link>
		<dc:creator>m.kanlic</dc:creator>
		<pubDate>Thu, 22 Nov 2007 02:06:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.bin-co.com/blog/2007/10/case-sensitivity-in-urls/#comment-219</guid>
		<description>I think you should go through that RFC again and look at the BNF.

That quote is for scheme section hence lower case in &quot;scheme names&quot; only, the scheme part is defined as alpha (both lower and upper case).

But I can agree it is arguable whether one or the other is &#039;better&#039;, ie. aiming at hefty URL spec here.</description>
		<content:encoded><![CDATA[<p>I think you should go through that RFC again and look at the BNF.</p>
<p>That quote is for scheme section hence lower case in &#8220;scheme names&#8221; only, the scheme part is defined as alpha (both lower and upper case).</p>
<p>But I can agree it is arguable whether one or the other is &#8216;better&#8217;, ie. aiming at hefty URL spec here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Binny V A</title>
		<link>http://www.bin-co.com/blog/2007/10/case-sensitivity-in-urls/comment-page-1/#comment-172</link>
		<dc:creator>Binny V A</dc:creator>
		<pubDate>Mon, 22 Oct 2007 09:12:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.bin-co.com/blog/2007/10/case-sensitivity-in-urls/#comment-172</guid>
		<description>@TipsoSaurus
That&#039;s true. WordPress is a much better option that creating a custom CMS.</description>
		<content:encoded><![CDATA[<p>@TipsoSaurus<br />
That&#8217;s true. WordPress is a much better option that creating a custom CMS.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TipsoSaurus</title>
		<link>http://www.bin-co.com/blog/2007/10/case-sensitivity-in-urls/comment-page-1/#comment-171</link>
		<dc:creator>TipsoSaurus</dc:creator>
		<pubDate>Mon, 22 Oct 2007 07:48:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.bin-co.com/blog/2007/10/case-sensitivity-in-urls/#comment-171</guid>
		<description>Not sure about if google will penalize the pages or not....but yeah one thing for sure....life is easier as most of us are using wordpress..otherwise people would have just cried..isn&#039;t it ?</description>
		<content:encoded><![CDATA[<p>Not sure about if google will penalize the pages or not&#8230;.but yeah one thing for sure&#8230;.life is easier as most of us are using wordpress..otherwise people would have just cried..isn&#8217;t it ?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
