httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David W. Gulley" <>
Subject Re: [users@httpd] Environment diference between UNIX and windows
Date Sat, 19 Jun 2004 23:52:18 GMT
I have (had) two reasons for asking:
   1) esthetics:
     I wanted to setup the directory of in-house test websites according 
to client and support requirements, but did not want that monstrosity 
carried over into what the CGI was handling.

   2) A problem with Perl's File::Find module:
      When running perl under taint mode, the Find routine fails due to 
the colon (:) in the windows pathname! A simple patch, but now the code 
is no longer "standard".

   I realize the difference is fundamental in how the two OSs work, 
however, I had hoped that using aliases and/or symbolic links, I could 
fool the CGI into not noticing the differences...

I assumed that a virtual host could "think" it was located at x when in 
reality it was at a/b/c/x. After all why does the server have to tell 
the "truth" about where things are located. !}


Robert Andersson wrote:

> David W. Gulley wrote:
>>   When retreiving the environment variables
>>      for example $ENV{SCRIPT_FILENAME}
>>   Unix gives a path with no drive:
>>       /home/user/public-html/cgi-bin/
>>   and windows includes the drive:
>>       C:/home/user/public-html/cgi-bin/
> I don't see how that is a difference. A full path on Windows includes the
> drive, while on *nix it doesn't (because they don't exist). That is not a
> difference in the semantics of the environment variable; it is a difference
> between the operating systems.
> If the drive letter wasn't included on Windows, it wouldn't be a full and
> valid path.
>>Bottom line:
>>    Does the server always report the actual physical path when
>>it provides the environment variables?
> I surely hope so. What else should it put there? Anything but the real path
> doesn't make sense. Without the drive letter, the path is useless unless you
> assume a drive letter (which is a bad idea).
> Bottom line: What are you trying to do? Please explain your goal and it
> might be easier to suggest how it should be accomplished.
> Regards,
> Robert Andersson

The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message