You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by "William A. Rowe, Jr." <wr...@lnd.com> on 2000/06/07 19:35:38 UTC
[Patch 1.3.13-dev] httpd.conf-dist & --win
I've re-synched the httpd.conf-dist-win to httpd.conf-dist, but found
a few particularities where it may make more sense to backport the --win
language to the stock httpd.conf.
Please take special care to note anything I've messed up in httpd.conf-dist
so I can fix before I commit.
[AddModule in the --win version doesn't recognize any names...
I'm investigating and will fix prior to this patch. Since
the Win32 binary is extremely standardized, I'm thinking this
is a good place to put the example so users -could- remove
dir_module in the event of a security hole such as was
discovered recently.]
RE: [Patch 1.3.13-dev] httpd.conf-dist & --win
Posted by "William A. Rowe, Jr." <wr...@lnd.com>.
> From: rbb@covalent.net [mailto:rbb@covalent.net]
> Sent: Wednesday, June 07, 2000 11:18 PM
>
> > >...
> > > One final addition to the Win32 updates, if everyone will
> entertain
> > > a very long entry in the .conf file for Windows only...
> >
> > Put it into the Windows-only file then. I don't want to see
> all that in the
> > non-Windows .conf.
>
> I thought the goal was to have only one config file finally.
> I don't mind
> having a big Windows only blurb in the config file, if it
> means we only
> have one config file.
An honorable and noble goal, no doubt :-)
Realistically, I think they are still two beasts (today, in 1.3.x)
I've minimized the number of lines of diffs, and I think that may
be as good as it gets.
Can we table that change till 2.0? (and this goes for -dist-nw as
well, when that is ported) I will begin looking in two weeks at
the 2.0 conf-dist stuff.
For 2.0, as well, can we assure that we can <IfDef WIN32>, or
<IfDef NETWARE> or whatever? Now that would be cool.
Re: [Patch 1.3.13-dev] httpd.conf-dist & --win
Posted by rb...@covalent.net.
> >...
> > One final addition to the Win32 updates, if everyone will entertain
> > a very long entry in the .conf file for Windows only...
>
> Put it into the Windows-only file then. I don't want to see all that in the
> non-Windows .conf.
I thought the goal was to have only one config file finally. I don't mind
having a big Windows only blurb in the config file, if it means we only
have one config file.
Ryan
_______________________________________________________________________________
Ryan Bloom rbb@apache.org
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------
RE: [Patch 1.3.13-dev] httpd.conf-dist & --win
Posted by "William A. Rowe, Jr." <wr...@lnd.com>.
> From: Greg Stein [mailto:gstein@lyra.org]
> Sent: Wednesday, June 07, 2000 10:34 PM
>
> > > From: William A. Rowe, Jr. [mailto:wrowe@lnd.com]
> > > Sent: Wednesday, June 07, 2000 12:44 PM
> > >
> > > > Please take special care to note anything I've messed up in
> > > > httpd.conf-dist
> > > > so I can fix before I commit.
>
> I noticed a couple problems, but just hadn't got to responding yet:
>
> 1) The IfModule stuff isn't necessary. Those sections will parse quite
> happily even when the modules are absent. Adding the
> IfModule just makes
> the .conf a bit more complicated.
On 1) you are absolutely correct (uh, duh.) I'm reversing that change
to the update now.
RE: [Patch 1.3.13-dev] httpd.conf-dist & --win
Posted by "William A. Rowe, Jr." <wr...@lnd.com>.
> From: Greg Stein [mailto:gstein@lyra.org]
> Sent: Wednesday, June 07, 2000 10:34 PM
>
> On Wed, Jun 07, 2000 at 10:28:42PM -0500, William A. Rowe, Jr. wrote:
> > > From: William A. Rowe, Jr. [mailto:wrowe@lnd.com]
> > > Sent: Wednesday, June 07, 2000 12:44 PM
> > >
> > > > I've re-synched the httpd.conf-dist-win to
> httpd.conf-dist, but found
> > > > a few particularities where it may make more sense to
> > > > backport the --win language to the stock httpd.conf.
> > > >
> > > > Please take special care to note anything I've messed up in
> > > > httpd.conf-dist
> > > > so I can fix before I commit.
> >
> > I intend to commit the changes I posted much earlier today by Friday
>
> I noticed a couple problems, but just hadn't got to responding yet:
>
> 1) The IfModule stuff isn't necessary. Those sections will parse quite
> happily even when the modules are absent. Adding the IfModule just makes
> the .conf a bit more complicated.
If that's true, that patch is out. I remember having problems, however,
if the modules aren't loaded. Do Win32 and Unix differ on this?
> 2) Don't refer to the file as "httpd.conf". Keep the "this
> file" thing. It
> is quite easy for a person to change the filename.
But we are describing a list of default behaviors, aren't we?
Can I perhaps add the phrase in parens
httpd.conf (i.e. this file, as specified by the -f directive) ???
Would that make it a little clearer?
> >...
> > One final addition to the Win32 updates, if everyone will entertain
> > a very long entry in the .conf file for Windows only...
>
> Put it into the Windows-only file then. I don't want to see
> all that in the non-Windows .conf.
Good God no! I would never afflict my Unix freinds with that :-) ROFL
Bill
Re: [Patch 1.3.13-dev] httpd.conf-dist & --win
Posted by Greg Stein <gs...@lyra.org>.
On Wed, Jun 07, 2000 at 10:28:42PM -0500, William A. Rowe, Jr. wrote:
> > From: William A. Rowe, Jr. [mailto:wrowe@lnd.com]
> > Sent: Wednesday, June 07, 2000 12:44 PM
> >
> > > I've re-synched the httpd.conf-dist-win to httpd.conf-dist, but found
> > > a few particularities where it may make more sense to
> > > backport the --win language to the stock httpd.conf.
> > >
> > > Please take special care to note anything I've messed up in
> > > httpd.conf-dist
> > > so I can fix before I commit.
>
> I intend to commit the changes I posted much earlier today by Friday
I noticed a couple problems, but just hadn't got to responding yet:
1) The IfModule stuff isn't necessary. Those sections will parse quite
happily even when the modules are absent. Adding the IfModule just makes
the .conf a bit more complicated.
2) Don't refer to the file as "httpd.conf". Keep the "this file" thing. It
is quite easy for a person to change the filename.
>...
> One final addition to the Win32 updates, if everyone will entertain
> a very long entry in the .conf file for Windows only...
Put it into the Windows-only file then. I don't want to see all that in the
non-Windows .conf.
Cheers,
-g
--
Greg Stein, http://www.lyra.org/
RE: [Patch 1.3.13-dev] httpd.conf-dist & --win
Posted by "William A. Rowe, Jr." <wr...@lnd.com>.
> From: William A. Rowe, Jr. [mailto:wrowe@lnd.com]
> Sent: Wednesday, June 07, 2000 12:44 PM
>
> > I've re-synched the httpd.conf-dist-win to httpd.conf-dist, but found
> > a few particularities where it may make more sense to
> > backport the --win language to the stock httpd.conf.
> >
> > Please take special care to note anything I've messed up in
> > httpd.conf-dist
> > so I can fix before I commit.
I intend to commit the changes I posted much earlier today by Friday
early a.m. Before I do, there is one horrible issue that keeps coming
up over, and over, and over in the windows NG, so...
One final addition to the Win32 updates, if everyone will entertain
a very long entry in the .conf file for Windows only...
(If you can't stand it, shorten it and post your replacement to the list :-)
#
# Apache parses all CGI scripts for the shebang line by default.
# This comment line, the first line of the script, consists of the symbols
# pound (#) and exclamation (!) followed by the path of the program that
# can execute this specific script. For a perl script, with perl.exe in
# the C:\Program Files\Perl directory, the shebang line should be:
#!c:/program files/perl/perl
# Note you _must_not_ indent the actual shebang line, and it must be the
# first line of the file. Of course, CGI processing must be enabled by
# the appropriate ScriptAlias or Options ExecCGI directives for the files
# or directory in question.
#
# However, Apache on Windows allows either the Unix behavior above, or can
# use the Registry to match files by extention. The command to execute
# a file of this type is retrieved from the registry by the same method as
# the Windows Explorer would use to handle double-clicking on a file.
#
# Each mechanism has it's own specific security weaknesses, from the means
# to run a program you didn't intent the website owner to invoke, and the
# best method is a matter of great debate.
#
# To enable the this Windows specific behavior (and therefore -disable- the
# equivilant Unix behavior), uncomment the following directive:
#
#ScriptInterpreterSource registry
#
# The directive above can be placed in individual <Directory> blocks or the
# .htaccess file, with either the 'registry' (Windows behavior) or 'script'
# (Unix behavior) option, and will override this server default option.
RE: [Patch 1.3.13-dev] httpd.conf-dist & --win
Posted by "William A. Rowe, Jr." <wr...@lnd.com>.
> -----Original Message-----
> From: William A. Rowe, Jr. [mailto:wrowe@lnd.com]
> Sent: Wednesday, June 07, 2000 12:36 PM
> To: new-httpd@apache.org
> Subject: [Patch 1.3.13-dev] httpd.conf-dist & --win
>
>
> I've re-synched the httpd.conf-dist-win to httpd.conf-dist, but found
> a few particularities where it may make more sense to
> backport the --win
> language to the stock httpd.conf.
>
> Please take special care to note anything I've messed up in
> httpd.conf-dist
> so I can fix before I commit.
>
> [AddModule in the --win version doesn't recognize any names...
> I'm investigating and will fix prior to this patch. Since
> the Win32 binary is extremely standardized, I'm thinking this
> is a good place to put the example so users -could- remove
> dir_module in the event of a security hole such as was
> discovered recently.]
For faster reading :-)
Here's the delta between conf-dist and conf-dist-win.
I will clena up this discrepancy in conf-dist before committing:
@@ -853,7 +841,7 @@
#
# Allow remote server configuration reports, with the URL of
-# http://servername/server-info (requires that mod_info.c be loaded).
+# http://servername/server-info (requires that mod_info.c be loaded).
# Change the ".your_domain.com" to match your domain to enable.
#
#<IfModule mod_info.c>
RE: [Patch 1.3.13-dev] httpd.conf-dist & --win
Posted by "William A. Rowe, Jr." <wr...@lnd.com>.
> From: Daniel S. Reichenbach [mailto:dsr@opensa.org]
> Sent: Wednesday, June 07, 2000 1:32 PM
>
> > [snap]...
> > #ClearModuleList
> > #AddModule mod_so.c mod_mime.c mod_access.c mod_auth.c
> > mod_negotiation.c
> > #AddModule mod_include.c mod_autoindex.c mod_dir.c mod_cgi.c
> > mod_userdir.c
> > #AddModule mod_alias.c mod_env.c mod_log_config.c mod_asis.c
> > mod_imap.c
> > #AddModule mod_actions.c mod_setenvif.c mod_isapi.c
> >
> > Sound appropriate?
>
> Sounds good, these are the basic ones.
They are the -only- ones... refer to os/win32/modules.c for the
master reference of what we compile in.
> BTW: i saw the diff with mod_info.c. Is it working under Win32?
On NT, and Win 9x according to Andrew :-)
RE: [Patch 1.3.13-dev] httpd.conf-dist & --win
Posted by "Daniel S. Reichenbach" <ds...@opensa.org>.
> [snap]...
> #ClearModuleList
> #AddModule mod_so.c mod_mime.c mod_access.c mod_auth.c
> mod_negotiation.c
> #AddModule mod_include.c mod_autoindex.c mod_dir.c mod_cgi.c
> mod_userdir.c
> #AddModule mod_alias.c mod_env.c mod_log_config.c mod_asis.c
> mod_imap.c
> #AddModule mod_actions.c mod_setenvif.c mod_isapi.c
>
> Sound appropriate?
Sounds good, these are the basic ones.
BTW: i saw the diff with mod_info.c. Is it working under Win32?
/me
--
Open Server Architecture project http://www.opensa.org/
Daniel S. Reichenbach dsr@opensa.org
RE: [Patch 1.3.13-dev] httpd.conf-dist & --win
Posted by "William A. Rowe, Jr." <wr...@lnd.com>.
> From: William A. Rowe, Jr. [mailto:wrowe@lnd.com]
> Sent: Wednesday, June 07, 2000 12:36 PM
>
> [AddModule in the --win version doesn't recognize any names...
> I'm investigating and will fix prior to this patch. Since
> the Win32 binary is extremely standardized, I'm thinking this
> is a good place to put the example so users -could- remove
> dir_module in the event of a security hole such as was
> discovered recently.]
Fixed... for the --win config the final product is:
#
# Apache Default Binary Distribution Modules
#
# The following modules are bound into the standard Apache binary distribution.
# To change the standard behavior, uncomment the following lines and modify the
# list of those specific modules to be enabled in the server.
#
# WARNING: This is an advanced option that may render your server inoperable!
# Do not use these directives without expert guidance.
#
#ClearModuleList
#AddModule mod_so.c mod_mime.c mod_access.c mod_auth.c mod_negotiation.c
#AddModule mod_include.c mod_autoindex.c mod_dir.c mod_cgi.c mod_userdir.c
#AddModule mod_alias.c mod_env.c mod_log_config.c mod_asis.c mod_imap.c
#AddModule mod_actions.c mod_setenvif.c mod_isapi.c
Sound appropriate?