httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Frank Faubert" <>
Subject Re: chdir isn't thead specific
Date Thu, 07 May 1998 02:04:55 GMT
Well, to be honest, our app started out on Unix and was then ported to NT.
We never bothered to test our app with CERN because hardly anyone uses it.
When we hit the problem with the NT port, we didn't think of
PATH_TRANSLATED, we just used the registry instead.  The next rev of our app
will definitely do something with PATH_TRANSLATED as a backup measure if its
not in the correct directory, but that doesn't help the thousands of users
that are using the current version, and all of our CD's that have already
been burned. :)

As for CGI/1.2, I am in agreement with the others that the more defined the
environment the better.  I think it would be good to force everyone to
conform to the standard.  As far as Apache goes, CGI/1.2 is not around right
now, so I'd take the chdir thing off of the showstopper list and deal with
it in Apache 2.0 / NSPR.


-----Original Message-----
From: Dean Gaudet <>
To: <>
Date: Wednesday, May 06, 1998 9:52 PM
Subject: Re: chdir isn't thead specific

>That's good information.  I'd suggest that CGI/1.2 is broken then for
>making this a requirement...
>I'm curious why you can't just use PATH_TRANSLATED?
>On Wed, 6 May 1998, Frank Faubert wrote:
>> >It seems like left as-is it could cause some problems for heavy CGI
>> >for 1.3.0 we either serialize this or declare that win32 CGI's need to
>> >their own chdir's.
>> >
>> I honestly wouldn't worry too much about chdir on Win32.  Most of the
>> servers out there (for Win32) do not do the chdir for you.  Our app uses
>> Windows registry to find the correct directory simply because all of the
>> Win32 servers behave differently.  Unix, however, is a very different
>> All of the servers (that I am aware of), except for CERN, do the chdir.
>> -Frank

View raw message