You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Joshua Slive <jo...@slive.ca> on 2001/12/13 19:31:38 UTC

RE: cvs commit: httpd-2.0/docs/manual/mod mod_cgi.html mod_cgid.html core.html

> From: wrowe@apache.org [mailto:wrowe@apache.org]
> wrowe       01/12/13 10:19:22
>
>   Modified:    docs/manual/mod mod_cgi.html mod_cgid.html core.html
>   Log:
>     A little loopy commit.  Refer mod_cgid users to the mod_cgi docs for
>     extra info, document the AcceptPathInfo impact in the
> PATH_INFO comments
>     of mod_cgi, and document it's configuration in core.

Just a loopy thought: Would it be useful to make the syntax
AcceptPathInfo On|Off|Default
where
AcceptPathInfo Default
was the same as not having the directive at all (a no-op in the code)?  This
would seem to make the tri-state nature a little clearer.

Joshua.

RE: cvs commit: httpd-2.0/docs/manual/mod mod_cgi.html mod_cgid.html core.html

Posted by Joshua Slive <jo...@slive.ca>.
> From: William A. Rowe, Jr. [mailto:wrowe@covalent.net]

> 
> From: "Joshua Slive" <jo...@slive.ca>
> Sent: Thursday, December 13, 2001 12:31 PM

> > Just a loopy thought: Would it be useful to make the syntax
> > AcceptPathInfo On|Off|Default
> > where
> > AcceptPathInfo Default
> > was the same as not having the directive at all (a no-op in the 
> code)?  This
> > would seem to make the tri-state nature a little clearer.
> 
> Would that be Default, or Unset?
> 

AcceptFilter in 1.3 has "default", but it doesn't really matter to me.

Joshua.

Re: cvs commit: httpd-2.0/docs/manual/mod mod_cgi.html mod_cgid.html core.html

Posted by "William A. Rowe, Jr." <wr...@covalent.net>.
From: "Joshua Slive" <jo...@slive.ca>
Sent: Thursday, December 13, 2001 12:31 PM


> > From: wrowe@apache.org [mailto:wrowe@apache.org]
> > wrowe       01/12/13 10:19:22
> >
> >   Modified:    docs/manual/mod mod_cgi.html mod_cgid.html core.html
> >   Log:
> >     A little loopy commit.  Refer mod_cgid users to the mod_cgi docs for
> >     extra info, document the AcceptPathInfo impact in the
> > PATH_INFO comments
> >     of mod_cgi, and document it's configuration in core.
> 
> Just a loopy thought: Would it be useful to make the syntax
> AcceptPathInfo On|Off|Default
> where
> AcceptPathInfo Default
> was the same as not having the directive at all (a no-op in the code)?  This
> would seem to make the tri-state nature a little clearer.

Would that be Default, or Unset?