|
|
Posted by Jonathan N. Little on 09/26/06 18:43
Alan J. Flavell wrote:
> Again this is wrong as stated. If I'm running e.g a CGI script on my
> Win32 Apache, then the script will see the actual URL that was
> presented, case and all, and can act accordingly. The distinction
> between differently-cased URLs disappears when the typical win32
> server maps URLs into the *file system*, it's true, but that's not
> because the URLs have magically become case-insensitive, but because
> the *file system* is, for these purposes, case-insensitive. The web
> doesn't know that, nor care about such internal server details -
> that's an important principle: URLs define a hierarchy of their own,
> which was designed to be server-agnostic.
It may be semantics here, and that the HTTP transaction will be
case-sensitive and it is the mapping file system case-insensitive
occurs. The file system does come to play here though. Yes your can
configure the web server to compensate, but I have really come across
any. In practice then the server is on a Windows platform and URIs sent
to the server in different case combinations, the web server may treat
as unique resources to fetch. The browser may (does) cache as unique
resources. But the Windows file systems will not fetch difference
resource is will all be the same file. So the "appearance" is that on
Windows platforms the URI may "seem" case-insensitive which can lull
less-savvy web designer to make errors that make their site not platform
independent.
--
Take care,
Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com
Navigation:
[Reply to this message]
|