phranque
msg:4520942 | 2:20 am on Nov 21, 2012 (gmt 0) |
everything after the hostname in a URL is case-sensitive and the trailing slash is significant and indicates directory structure or hierarchical structure in the path.
those are three different URLs.
on windows server, you must Configure Case Sensitivity for File and Folder Names:
http://technet.microsoft.com/en-us/library/cc725747.aspx [technet.microsoft.com]
i would strongly suggest going with all lowercase in the URL and internally rewrite all requests with uppercase in the URL to a redirect script.
make sure all non-canonical requests are redirected in one hop.
|
incrediBILL
msg:4521988 | 8:48 pm on Nov 23, 2012 (gmt 0) |
| everything after the hostname in a URL is case-sensitive |
|
While that is generally true when working in the real world, I thought Windows boxes were configured case-insensitive by default?
|
phranque
msg:4522084 | 3:12 am on Nov 24, 2012 (gmt 0) |
it's the Windows Server OS that is case-insensitive by default, which is a perfect example of why you should look away from MS for proper implementation of HTTP protocol or best web practices.
so yes - "out of the box" it will happily serve 200 OKs for 2**N - 1 non-canonical casing combinations but that doesn't make it optimal or correct or recommended.
the search engines are where it gets "real world" here and they will index those as different URLs which means duplicate content.
your browser won't style your anchor text as "visited" unless the casing of the url matches.
windows server is not the "real world" - it's more like disneyworld.
|
|
