Re: CGI/1.1 draft
john@math.nwu.edu (John Franks)
Errors-To: listmaster@www0.cern.ch
Date: Tue, 1 Mar 1994 22:38:13 --100
Message-id: <9403012135.AA03825@hopf.math.nwu.edu>
Errors-To: listmaster@www0.cern.ch
Reply-To: john@math.nwu.edu
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: john@math.nwu.edu (John Franks)
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Re: CGI/1.1 draft
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Content-Length: 965
According to Ari Luotonen:
>
> > I like the idea of a data root directory environment variable. At
> > user request I have already implemented this as a non-standard feature
> > in GN.
>
> Then what would I do? cern_httpd doesn't have a single document
> root, and there is no reason why it should. I would like to see
> DOCUMENT_ROOT as a server-specific feature rather than dictated
> by the spec.
>
Well, there is no reason that the value of the DOCUMENT_ROOT can't
depend on the URL, so you could accomodate multiple roots. But
I don't have strong feelings on this. I would be happy with having
it be server-specific.
You should be aware however, that (as someone described recently in
a www-talk post) script writers are taking PATH_TRANSLATED and
trying to delete PATH_INFO from the end to obtain a document root.
They are doing this because their scripts need to access more than
one asscociated file. How will this work with cern_httpd?
John