On Monday 07 January 2002 01:05 pm, Sander Striker wrote: > > From: Ryan Bloom [mailto:[EMAIL PROTECTED]] > > Sent: 07 January 2002 22:00 > > To: [EMAIL PROTECTED]; William A. Rowe, Jr. > > Subject: Re: [PATCH] Allow DocumentRoot within Location blocks > > > > > > On Monday 07 January 2002 11:55 am, William A. Rowe, Jr. wrote: > > > From: "Rodent of Unusual Size" <[EMAIL PROTECTED]> > > > Sent: Monday, January 07, 2002 1:47 PM > > > > > > > > > > Ryan Bloom wrote: > > > > > > > > > > Note that I said the module needed to be written correctly. > > > > > Mod_status doesn't have a map_to_storage hook, which would > > > > > be required to avoid the stats. > > > > > > > > I'm in favour of a mechanism that doesn't require every single > > > > generated-content module to be rewritten to include an essentially > > > > duplicate function. > > > > I'm in favor of doing this in the code and not forcing every administrator to > > reconfigure their server to get this functionality. Understand that introducing > > the DocumentRoot directive inside a <Location> container doesn't remove the > > stats automatically, it requires that every admin change their mod_status config > > to: > > > > <Location /server-status> > > DocumentRoot unset > > SetHandler server-status > > </Location> > > Actually, no. The default is 'unset' in <Location> blocks.
If that were the case, then the "DocumentRoot unset" syntax would be completely unnecessary. That would still make me wonder exactly what problem we are trying to solve with this. Ryan ______________________________________________________________ Ryan Bloom [EMAIL PROTECTED] Covalent Technologies [EMAIL PROTECTED] --------------------------------------------------------------
