jdMorgan - 3:32 pm on Jan 8, 2007 (gmt 0)  RFC 2396 [faqs.org]
is the controlling document for these issues.  In practice, the
schema ("http") and authority (server name or "domain") strings
are always sent as lowercase-only by properly-implemented
clients, but treated in a case-insensitive manner by servers and
all intervening network components.  However, the same is not
true for the path component -- the "filename" portion of the
URL.  Therefore, a request for
"http://HTTPD.APACHE.ORG/DoCs/1.3/" will arrive at the server as
"http://httpd.apache.org/DoCs/1.3/" -- Note that only the scheme
and the authority have been lowercased, and the path remains as-
linked (try it with your own domain, and observe the browser
address bar). Unless the server uses MultiViews or has rules
similar to those above, this request will fail if the "filename"
case is incorrect. (Note that if the server OS is Windows it
will not fail, because Windows treats filenames in a case-
insensitive manner.)  So it is Googlebot (as a client) t