james.a.augeri@honeywell.com wrote:
> I have just built an Apache (1.3.37) server on a new Solaris box
> (v-490; Solaris 10). This machine also runs ColdFusion 5.0, Perl 5.8.4,
> and a few other doo-dads. I have several CF pages that make use of the
> CGI variable PATH_TRANSLATED, and have noticed that the value is not
> getting populated by the Server & Client. This *new* Web server is a
> replacement for an existing box that is to be retired. (The reason for
> Apache 1.3.37 is the CF 5.0; it is not compatible with Apache 2.x)
> Apache was built from the source distribution, as have all prior
> versions I have run here.
> I have been reading these groups, other on line forums, various web
> rings and every other resource I can find to try and identify just WHY
> Apache would not be setting these variables; all to no avail.
> Here is what I have tried:
> Compared old servers httpd.conf to the new one line-by-line looking for
> discrepancies (none found)
> Installed the OLD servers Apache version (1.3.33) on the new hardware;
> used the same config file; no difference. (Old server hardware is a Sun
> Enterprise E-4500 running Solaris 2.6)
> I've included the <cfdump var = "#CGI#"> directive in a test page to
> confirm the missing info;
> I've used the "test-cgi" script that comes with Apache to confirm
> PATH_TRANSLATED is not populated.
> I've used an "shtml" page with settings to confirm as well.
> All tests I've run indicate this to be the case. Interesting enough,
> the DOUCMENT_ROOT variable is also not being seen, nor is PATH_INFO.
>
> If I run the same test pages on the existing box (the current
> production server) everything works as I would expect. All the CGI
> variables are populated as I have come to expect, and are usable in the
> CF templates and CGI scripts that are intended to make use of them. I
> have built several incarnations of Apache over the years, starting with
> 1.2.something, but this is the first time I have ever run into anything
> like this. Could this somehow be related to the new version of
> Solaris? What else should I look at?

I dont know - All I can say is that Solaris 9 behaves the same way.
I tried a few hacks but could not get anything to appear for PATH_INFO
and many other env vars. Even if I gave "apache" user a shell (!) and
inserted
a value in apachectl. Same with version 2. So its not Solaris 10 thats
doing it.. : >
Were it my "problem" I guess Id compile with -g set a few break points
and see whats NOT
happening as you wish.