[In order for any reply to be added to the PR database, ] [you need to include <[EMAIL PROTECTED]> in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ] [If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request ] [from a developer. ] [Reply only with text; DO NOT SEND ATTACHMENTS! ]
Synopsis: PATH_TRANSLATED is shifted to lower case from mixed case Comment-Added-By: coar Comment-Added-When: Fri Oct 2 11:13:40 PDT 1998 Comment-Added: No, it is not simple. If you think it is, you don't understand all of the issues involved. On Unix platforms PATH_TRANSLATED's case is preserved because the filesystem is case sensitive; "X" and "x" are different files, and PATH_TRANSLATED must be able to distinguish between them. On Win32, "X" and "x" are the same file, and Apache needs to be able to determine *that* for purposes of access checking, et cetera -- so Win32 filenames are canonicalised into an all-lowercase format so that comparisons will always be accurate. PATH_TRANSLATED is generated on the back end of this process, and thus inherits the transformed name. You should not depend upon PATH_TRANSLATED in any event. Try using REQUEST_URI and DOCUMENT_ROOT, both of which are available to CGI and aren't transformed, to construct the path you need. PATH_TRANSLATED is only intended to provide *a* working path to the file -- not necessarily *the* working path. If you depend upon it, you are trying to interpret Web locations using filesystem semantics -- which isn't guaranteed to work, as you have found.
