W3C home > Mailing lists > Public > public-qa-dev@w3.org > July 2005

Re: validator/httpd/conf httpd.conf,1.24,1.25

From: Ville Skyttä <ville.skytta@iki.fi>
Date: Fri, 22 Jul 2005 00:50:48 +0300
To: QA Dev <public-qa-dev@w3.org>
Message-Id: <1121982648.5196.27.camel@localhost.localdomain>

On Thu, 2005-07-21 at 10:59 +0900, olivier Thereaux wrote:

> Thanks, Ville. On a related note, I have been wondering for a long  
> time why our httpd snippet had:
> 
> # Tell httpd that "check" is a CGI script.
> <Location "/w3c-validator/check">
>    SetHandler            cgi-script
> </Location>
> 
> And not just:
> ScriptAlias /w3c-validator/check "/usr/share/w3c-markup-validator/ 
> httpd/cgi-bin/check"
> 
> Given that w3c-validator/ is an alias to the htdocs directory, it  
> means one has to copy the check script into the htdocs, for which I  
> can't find a good reason. Was that to make it mod_perl friendly? I  
> can't see why.

The above was convenient because some mod_perl directives needed to go
into the <Location> section (or somewhere, but anyway).  Now that the
mod_perl stuff is gone, there's no need for it, ScriptAlias will do.
Read below for more thoughts about where the scripts should IMHO be
installed...

> Anyway, unless anyone objects, I think I will use the scriptalias  
> directive instead of the SetHandler in what we will ship for 0.7.0.
> 
> Any thought on this?

Telepathy :).  I actually prepared a patch yesterday and committed a few
minutes ago before reading this message.

If you look at the httpd.conf snippet in CVS now, I've opted to put
check and sendfeedback.pl not in $Base/htdocs/ but $Base/cgi-bin/, and
ScriptAlias them.  I anticipate it could theoretically (OTOH untested
right now) be easier this way wrt. SELinux, and removes the need to
allow ExecCGI in htdocs.  Note: I dropped the "httpd" directory from
between $Base and cgi-bin for cosmetic reasons; it serves no real
purpose there.  I think it doesn't make installation much if at all
harder either.

Additionally, I'm planning to work on the installation documentation
which appears pretty bitrotten at the moment.  It would be cool if you
and others could check the above installation layout plan and let me
know what you think before I start hacking the docs.

Oh, one more thing: do we need httpd/conf/mime.types in CVS and the
tarball for something?
Received on Thursday, 21 July 2005 21:50:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 19 August 2010 18:12:45 GMT