Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<h1>IIS <em>is</em> case-sensitive...</h1> <p>...but not for files.</p> <p>It is a misnomer that IIS is case-insensitive, it is the Windows file system that is case-insensitive, not IIS. If a URL contains a file path then IIS asks Windows if the file exists and the OS responds without regard to letter case. There is no way to "enable" case sensitivity for file names in Windows.</p> <p>But for other than <em>real</em> file paths, IIS is 100% case-sensitive. The case of URL characters is passed to the IIS pipeline intact. It is up to the web application whether or not case-sensitivity exists. But good practice says you don't want <code>/page1</code> to be different than <code>/PAGE1</code>.</p> <p>ASP.NET is case-insensitive to query string variable names. AGAIN, this is <em>not</em> IIS. It is the application (ASP.NET) that is case-insensitive.</p> <h1>Summary</h1> <p>Static file paths are not case-sensitive (due to Windows OS, not IIS):</p> <pre><code>http://example.com/sUbdiRectoRy/FILe.aspx </code></pre> <p>HOWEVER, portions of the URL not participating in the file path <em>are</em> case-sensitive (everything after <code>file.aspx</code> below except for the 'x' parameter because .aspx is an ASP.NET resource):</p> <pre><code>http://example.com/sUbdiRectoRy/FILe.aspx/Extra/Tail?x="query parameter" </code></pre> <p>URLs that are dynamically generated by re-writes, HttpModules, etc. are also case-sensitive if the application is case-sensitive. This is usually not best practice as these two URLs would refer to two separate web pages:</p> <pre><code>http://example.com/2012/01/23/blog-article http://example.com/2012/01/23/BLOG-ARTICLE </code></pre>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload