title: Why are cookie paths case sensitive?
body: <p>I've realised for the first time a couple of weeks ago that when setting an http cookie, while the domain name is not case sensitive, the path is. </p>
  
  <p>So a while a cookie stored for</p>
  
  <p><code>http://SomeWebSite.com</code></p>
  
  <p>can be read using</p>
  
  <p><code>http://somewebsite.com</code></p>
  
  <p>a cookie stored for</p>
  
  <p><code>http://somewebsite.com/SomePath</code></p>
  
  <p><em>cannot</em> be read using</p>
  
  <p><code>http://somewebsite.com/somepath</code></p>
  
  <p>It would simply not be found.</p>
  
  <p>As this is clearly stated in the RFC (see point 3.3.3 <a href="http://www.ietf.org/rfc/rfc2965.txt" rel="noreferrer">here</a>) I doubt that's an oversight, but as a user I'm not trained to treat urls as case sensitive text and web servers, as far as I can tell, don't seem to mind either way, and would serve pages just fine; so I'm left wondering - what is the rationale behind this decision? </p>
  
  <p>Anyone can shed some light?</p>