httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe Jr." <>
Subject Re: SetVirtualDocumentRoot / per request document root / context root?
Date Mon, 13 Dec 2010 17:06:41 GMT
On 12/13/2010 4:35 AM, Stefan Fritsch wrote:
> On Monday 13 December 2010, Ondřej Surý wrote:
>> On Mon, Dec 13, 2010 at 04:15, William A. Rowe Jr. <wrowe@rowe-
>> wrote:
>>> On 12/12/2010 4:23 PM, Stefan Fritsch wrote:
>>>> On Wednesday 10 November 2010, Stefan Fritsch wrote:
>>>>>> The frequency with which this gets asked seems to make it
>>>>>> worthwhile doing something, even if this patch isn't the right
>>>>>> thing to do.
>>>>> Maybe the larger solution of having a document_root field in
>>>>> the request_rec would be better. Has anyone had a chance to
>>>>> look at Ondrej's patch, already? I didn't get around to doing
>>>>> it, yet.
>>>> I have looked at the patch and it looks reasonable. The fact
>>>> that two known modules (mod_vhost_ldap and mod_ftp) copy the
>>>> whole server_rec just to change the document root means that
>>>> this feature is needed.
>>>> Well, at least for mod_ftp it is...
>>>> I am wondering if the people who want this for mod_vhost_*
>>>> actually want something else, namely an easy way to get the
>>>> root dir of a web application in php/cgi/whatever...
>>>> What about this idea:
>>>> Add two new cgi env variables: CONTEXT_ROOT and
>>>> CONTEXT_ROOT_PATH (or APP_ROOT/APP_ROOT_PATH or ...). And add a
>>>> new config directive
>>> Feh... DOCUMENT_ROOT was bad enough, do we have to persist the
>>> concept of sharing such things with the app?  For that matter,
>>> what are the vars that are used in app doc models today, why
>>> would we have to invent this again?
> These things are handled nicely in the JEE world by AJP and the 
> servlet container. They don't seem to work all that well in the 
> CGI-/PHP-world.

So before inventing semantics, pointers to the Servlet semantics and/or
the ASP.NET semantics would be appropriate, and discuss an established
model and naming conventions you've already identified as working nicely.

View raw message