Return-Path: owner-new-httpd Received: by taz.hyperreal.com (8.6.10/8.6.5) id AAA02724; Fri, 26 May 1995 00:06:29 -0700 Received: from eat.organic.com by taz.hyperreal.com (8.6.10/8.6.5) with ESMTP id AAA02717; Fri, 26 May 1995 00:06:27 -0700 Received: (from brian@localhost) by eat.organic.com (8.6.11/8.6.9) id AAA12975; Fri, 26 May 1995 00:06:35 -0700 Date: Fri, 26 May 1995 00:06:35 -0700 (PDT) From: Brian Behlendorf Subject: cwdir a part of CGI spec? To: new-httpd@apache.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-new-httpd@apache.org Precedence: bulk Reply-To: new-httpd@apache.org Even though this is just related to CGI I thought I'd post it here. This morning an issue came up where a bunch of scripts I had written for a client failed to work, the reason being that NCSA and Apache do a cwdir to the script's directory before launching the script, while NetSite doesn't. Thus, if I have one Perl script that "requires" another and references it locally (just like the way HTML files can point to each other locally), it'll work on Apache and NCSA but not on Netsite. I.e.: In directory /path/scripts/ I have common.pl script.cgi where common.pl is a perl file that sets config information and/or has common subroutines for the other scripts to use. I should be able to say require "./common.pl" in script.cgi. With NetSite (and I'm sorry to single it out, Rob, I'm sure others have this problem) I'd have to explicitly state require "/path/scripts/common.pl" which suddenly make my scripts a lot less portable. Should doing a cwdir to a script's directory be a part of the CGI spec? Brian --=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-- brian@organic.com brian@hyperreal.com http://www.[hyperreal,organic].com/