RE: [PATCH] Apache2 httpd.conf
Günter Knauf [mailto:[EMAIL PROTECTED]] wrote: > unfortunately we have symlinks only on *nix platforms, so for > all other platforms this isnt a solution... > Guenter. Unices all? have symlinks and NT supports lins too. Then still people could instead of symlinking the data copy the configs in and out of the enabled dir. On debian they got the two simple commands for that, apachectl could be made to do it to. Greets, Jeroen > > Better do the configs the 'debian way' then: > > > /etc/apache2/ containing: > > > apache2.conf : default config for running Apache2 minimally. > > ports.conf : "Port 443" etc directives > > httpd.conf : local site extra's > > modules-available/ : containing a config file per module > > modules-enabled/ : containing symlinks to the modules-available > > directory > > > Now if you want a module enabled; you can symlink it, easy > and obvious > > configging for everybody ;) > > The apache2.conf "includes" the ports.conf + httpd.conf + > > modules-available ofcourse. > > As for packagers, let your apache module depend on the main apache > > package and install your module's > > config into the available dir, then _ask_ the user if they want it > > enabled at once.
Re: [PATCH] Apache2 httpd.conf
On Fri, Jun 21, 2002 at 09:34:08AM -0700, Aaron Bannert wrote: > +1 for removing the mod-status and mod-info sections from the default > config entirely. In an ideal world there would be no default config, Blech. -0 on removing it from the default configuration. IMHO, it's useful - just leave it commented out. And, on the other topic, a big whopping -0 for splitting out our default config to multiple files. We've gone over this before and I'm totally against multiple default configuration files. And, the posted mod_deflate configuration is *way* too complicated. I'd just use: AddOutputFilterByType DEFLATE text/html My $.02. -- justin
Re: [PATCH] Apache2 httpd.conf /2
On Fri, Jun 21, 2002 at 02:55:07PM +0200, Günter Knauf wrote: > Hi, > I've been asked now a couple of times for a configuration sample for mod_deflate; >and since mod_deflate is now a 'normal' module and no more experimental I think there >should be a sample in the httpd.conf; if you dont think so at least a sample as below >should appear in the docs to mod_deflate... I think this thing would be perfect for a document, or perhaps a collection of example configuration files. -aaron
Re: [PATCH] Apache2 httpd.conf
On Fri, Jun 21, 2002 at 10:26:46AM -0400, Joshua Slive wrote: > Günter Knauf wrote: > > >the patch doesnt enable the modules, just only it's easier to enable them > >with only removing one # at the load command...; also I'm more thinking of > >disabling the modules after I have already used them; and if I then comment > >the load command I must also comment six config lines per module because > >the config isnt blocked with IfModule... > > Ahhh, but you forget that not everyone uses DSO modules. Many people > compile the modules into the server, and for them the module is active > regardless of the LoadModule line. Right. It would be nice if we had one way to load a module, and another way to enable it. This is the same debate as using vs. . +1 for removing the mod-status and mod-info sections from the default config entirely. In an ideal world there would be no default config, since the server defaults would allow simple serving of static pages. Config parameters could then be added to extend or override the defaults, and there would be one way to configure the server (and not two as we have it now). -aaron
RE: [PATCH] Apache2 httpd.conf
unfortunately we have symlinks only on *nix platforms, so for all other platforms this isnt a solution... Guenter. > Better do the configs the 'debian way' then: > /etc/apache2/ containing: > apache2.conf : default config for running Apache2 minimally. > ports.conf : "Port 443" etc directives > httpd.conf : local site extra's > modules-available/ : containing a config file per module > modules-enabled/ : containing symlinks to the modules-available > directory > Now if you want a module enabled; you can symlink it, easy and obvious > configging for everybody ;) > The apache2.conf "includes" the ports.conf + httpd.conf + > modules-available ofcourse. > As for packagers, let your apache module depend on the main apache > package and install your module's > config into the available dir, then _ask_ the user if they want it > enabled at once.
Re: [PATCH] Apache2 httpd.conf
> Bill Stoddard wrote: > > > > Playing devil's advocate :-) mod_status and mod_info should NOT be loaded by >default. > > > > Agreed! Wouldn't this change set things up so that if someone does > a compile with mod_status and mod_info included, the resultant > config file would make them active? That was my understanding. > If not, then, well... (in my best Emily Latella voice)... "never mind" :) > You're right. If mod_status and mod_info are compiled in, this change would make them active. Not good. I am also a fan of minimalist config files. Bill
Re: [PATCH] Apache2 httpd.conf
Günter Knauf wrote: >>Ahhh, but you forget that not everyone uses DSO modules. Many people >>compile the modules into the server, and for them the module is active >>regardless of the LoadModule line. > > Ok, that was the point I missed and convinces me that it's not such a good idea >then... > > then let's make another suggestion: > let's create a modules.conf and move these configs into it, and perhaps also the >mod_deflate config; then this conf can easily be included from the httpd.conf, and >httpd.conf becomes simpler... Yes, I believe that on the docs list Rich was thinking about something along the lines of a conf/examples/ directory where we could put all sorts of config snippets. I don't think anyone would have a problem with that, although it shouldn't replace having good examples in the documentation. Joshua.
RE: [PATCH] Apache2 httpd.conf
Günter Knauf [mailto:[EMAIL PROTECTED]] wrote: > > Ahhh, but you forget that not everyone uses DSO modules. > Many people > > compile the modules into the server, and for them the > module is active > > regardless of the LoadModule line. > Ok, that was the point I missed and convinces me that it's > not such a good idea then... > > then let's make another suggestion: > let's create a modules.conf and move these configs into it, > and perhaps also the mod_deflate config; then this conf can > easily be included from the httpd.conf, and httpd.conf > becomes simpler... Better do the configs the 'debian way' then: /etc/apache2/ containing: apache2.conf : default config for running Apache2 minimally. ports.conf : "Port 443" etc directives httpd.conf : local site extra's modules-available/ : containing a config file per module modules-enabled/ : containing symlinks to the modules-available directory Now if you want a module enabled; you can symlink it, easy and obvious configging for everybody ;) The apache2.conf "includes" the ports.conf + httpd.conf + modules-available ofcourse. As for packagers, let your apache module depend on the main apache package and install your module's config into the available dir, then _ask_ the user if they want it enabled at once. Greets, Jeroen
Re: [PATCH] Apache2 httpd.conf
> Ahhh, but you forget that not everyone uses DSO modules. Many people > compile the modules into the server, and for them the module is active > regardless of the LoadModule line. Ok, that was the point I missed and convinces me that it's not such a good idea then... then let's make another suggestion: let's create a modules.conf and move these configs into it, and perhaps also the mod_deflate config; then this conf can easily be included from the httpd.conf, and httpd.conf becomes simpler... Guenter.
Re: [PATCH] Apache2 httpd.conf
On Fri, 21 Jun 2002, [ISO-8859-1] Günter Knauf wrote: > the patch doesnt enable the modules, just only it's easier to enable > them with only removing one # at the load command...; That assumes you compile DSO's. > also I'm more thinking of disabling the modules after I have already > used them; and if I then comment the load command I must also comment > six config lines per module because the config isnt blocked with > IfModule... Well, THAT could be fixed, sure. :) But I'm iffy on whether it should be because I agree with Joshua that too many IfModule's just makes things hard to understand. --Cliff
Re: [PATCH] Apache2 httpd.conf
Günter Knauf wrote: > the patch doesnt enable the modules, just only it's easier to enable them with only >removing one # at the load command...; also I'm more thinking of disabling the >modules after I have already used them; and if I then comment the load command I must >also comment six config lines per module because the config isnt blocked with >IfModule... Ahhh, but you forget that not everyone uses DSO modules. Many people compile the modules into the server, and for them the module is active regardless of the LoadModule line. > why should somebody load the modules and waste memory if he doesnt use them?? And >again: the patch makes it erasier to enable / disable the modules, it does _NOT_ >enable them by default. What people "should" do and what people actually do are very different things. Many people have many superfluous modules in their build, and we need to make sure that it doesn't hurt them too badly. Joshua.
Re: [PATCH] Apache2 httpd.conf
Bill Stoddard wrote: > > Playing devil's advocate :-) mod_status and mod_info should NOT be loaded by >default. True. But even if they aren't, adding them in active sections in the default config is too dangerous in my opinion. Those are security-sensitive modules, and there is absolutely no way to know that the security policy that we have in the default config is anywhere near what is needed by any particular site. I might be willing to bend a little if it was changed to "Allow from 127.0.0.1", but even then, I don't think it is a good idea. Two general points: - I don't believe that it is a good practice to have the configuration of the server changed by simply adding a module. It should require an active change to httpd.conf to change the configuration. (We violate this policy already in some case; for example, mod_unique_id does its work regardless of the config file.) - sections need to be used very carefully in the default config. They seem to be misunderstood by users. For example, I see many people adding things like RewriteEngine On ... Sometimes these people don't have mod_rewrite compiled into the server, and then instead of getting a useful error message about the directive not being understood, the server silently ignores them. In other words, we are setting a bad example by liberally using and we are confusing users. Joshua
Re: [PATCH] Apache2 httpd.conf
> Cliff Woolley wrote: >> >> On Fri, 21 Jun 2002, Bill Stoddard wrote: >> >> >> can we apply this simple patch so that we dont have to always >> >> uncomment >> >> 12 lines for getting mod_info / mod_status working? >> > >> > +1 >> >> -0.5 Our default config has always taken a minimalist policy, I believe. the patch doesnt enable the modules, just only it's easier to enable them with only removing one # at the load command...; also I'm more thinking of disabling the modules after I have already used them; and if I then comment the load command I must also comment six config lines per module because the config isnt blocked with IfModule... > Having it loaded and having it active and enabled are, IMO, 2 > separate entities. I would prefer not having a generic build which > happens to include these modules be active by default, so I'm like > -0.75 about this :) why should somebody load the modules and waste memory if he doesnt use them?? And again: the patch makes it erasier to enable / disable the modules, it does _NOT_ enable them by default. Guenter.
Re: [PATCH] Apache2 httpd.conf
Bill Stoddard wrote: > > Playing devil's advocate :-) mod_status and mod_info should NOT be loaded by >default. > Agreed! Wouldn't this change set things up so that if someone does a compile with mod_status and mod_info included, the resultant config file would make them active? That was my understanding. If not, then, well... (in my best Emily Latella voice)... "never mind" :) -- === Jim Jagielski [|] [EMAIL PROTECTED] [|] http://www.jaguNET.com/ "A society that will trade a little liberty for a little order will lose both and deserve neither" - T.Jefferson
Re: [PATCH] Apache2 httpd.conf
> > > > On Fri, 21 Jun 2002, Bill Stoddard wrote: > > > > >> can we apply this simple patch so that we dont have to always uncomment > > >> 12 lines for getting mod_info / mod_status working? > > > > > > +1 > > > > -0.5 Our default config has always taken a minimalist policy, I believe. > > > > Having it loaded and having it active and enabled are, IMO, 2 > separate entities. I would prefer not having a generic build which > happens to include these modules be active by default, so I'm like > -0.75 about this :) Playing devil's advocate :-) mod_status and mod_info should NOT be loaded by default. Bill
Re: [PATCH] Apache2 httpd.conf
> On Fri, 21 Jun 2002, Bill Stoddard wrote: > > >> can we apply this simple patch so that we dont have to always uncomment > >> 12 lines for getting mod_info / mod_status working? > > > > +1 > > -0.5 Our default config has always taken a minimalist policy, I believe. > > --Cliff > Is there a reason that we should not completely remove the commented out mod_status and mod_info config directives from the default config then? I don't see that the proposed patch adds any complexity what so ever and it makes it a bit easier to get mod_info and mod_status enabled. Bill
Re: [PATCH] Apache2 httpd.conf
Cliff Woolley wrote: > > On Fri, 21 Jun 2002, Bill Stoddard wrote: > > >> can we apply this simple patch so that we dont have to always uncomment > >> 12 lines for getting mod_info / mod_status working? > > > > +1 > > -0.5 Our default config has always taken a minimalist policy, I believe. > Having it loaded and having it active and enabled are, IMO, 2 separate entities. I would prefer not having a generic build which happens to include these modules be active by default, so I'm like -0.75 about this :) -- === Jim Jagielski [|] [EMAIL PROTECTED] [|] http://www.jaguNET.com/ "A society that will trade a little liberty for a little order will lose both and deserve neither" - T.Jefferson
Re: [PATCH] Apache2 httpd.conf
On Fri, 21 Jun 2002, Bill Stoddard wrote: >> can we apply this simple patch so that we dont have to always uncomment >> 12 lines for getting mod_info / mod_status working? > > +1 -0.5 Our default config has always taken a minimalist policy, I believe. --Cliff
Re: [PATCH] Apache2 httpd.conf /2
My vote is to leave this out of the config file but certainly put it in the doc.
Bill
Hi,
I've been asked now a couple of times for a configuration sample for mod_deflate; and
since mod_deflate is now a 'normal' module and no more experimental I think there
should
be a sample in the httpd.conf; if you dont think so at least a sample as below should
appear in the docs to mod_deflate...
Ian, do you think the sample is ok so?
--- httpd-win.conf.orig Fri Jun 21 14:26:30 2002
+++ httpd-win.conf Fri Jun 21 14:44:40 2002
@@ -169,6 +169,7 @@
LoadModule userdir_module modules/mod_userdir.so
#LoadModule usertrack_module modules/mod_usertrack.so
#LoadModule vhost_alias_module modules/mod_vhost_alias.so
+#LoadModule deflate_module modules/mod_deflate.so
#LoadModule ssl_module modules/mod_ssl.so
#
@@ -948,3 +949,24 @@
#ErrorLog logs/dummy-host.example.com-error_log
#CustomLog logs/dummy-host.example.com-access_log common
#
+
+#
+# Configuration for mod_deflate
+
+# DeflateFilterNote - Set a note to report on compression ratio
+DeflateFilterNote deflate_ratio
+LogFormat "%h %l %u %t \"%r\" %>s %b mod_deflate: %{deflate_ratio}n pct."
common_with_deflate_info
+CustomLog logs/deflate.log common_with_deflate_info
+# Set the Deflate window size (1-15)
+DeflateWindowSize 10
+# Set the Deflate Memory Level (1-9)
+DeflateMemLevel 6
+# Here is an example of enabling compression for the Apache documentation:
+
+SetEnv gzip-only-text/html 1
+SetOutputFilter DEFLATE
+
+
+# End of mod_deflate.
+
+
--- httpd-nw.conf.orig Fri Jun 21 14:29:15 2002
+++ httpd-nw.conf Fri Jun 21 14:46:07 2002
@@ -139,6 +139,7 @@
#LoadModule unique_id_module modules/uniqueid.nlm
#LoadModule usertrack_module modules/usertrk.nlm
#LoadModule vhost_alias_module modules/vhost.nlm
+#LoadModule deflate_module modules/deflate.nlm
#
# ExtendedStatus controls whether Apache will generate "full" status
@@ -948,3 +949,24 @@
#ErrorLog logs/dummy-host.example.com-error_log
#CustomLog logs/dummy-host.example.com-access_log common
#
+
+#
+# Configuration for mod_deflate
+
+# DeflateFilterNote - Set a note to report on compression ratio
+DeflateFilterNote deflate_ratio
+LogFormat "%h %l %u %t \"%r\" %>s %b mod_deflate: %{deflate_ratio}n pct."
common_with_deflate_info
+CustomLog logs/deflate.log common_with_deflate_info
+# Set the Deflate window size (1-15)
+DeflateWindowSize 10
+# Set the Deflate Memory Level (1-9)
+DeflateMemLevel 6
+# Here is an example of enabling compression for the Apache documentation:
+
+SetEnv gzip-only-text/html 1
+SetOutputFilter DEFLATE
+
+
+# End of mod_deflate.
+
+
Re: [PATCH] Apache2 httpd.conf
+1 - Original Message - From: "Günter Knauf" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, June 21, 2002 8:48 AM Subject: [PATCH] Apache2 httpd.conf Hi, can we apply this simple patch so that we dont have to always uncomment 12 lines for getting mod_info / mod_status working? thanks! --- httpd-win.conf.orig Thu Jun 13 20:39:04 2002 +++ httpd-win.conf Fri Jun 21 14:26:30 2002 @@ -850,24 +850,28 @@ # Allow server status reports, with the URL of http://servername/server-status # Change the ".@@DomainName@@" to match your domain to enable. # -# -#SetHandler server-status -#Order deny,allow -#Deny from all -#Allow from .@@DomainName@@ -# + + +SetHandler server-status +Order deny,allow +Deny from all +Allow from .@@DomainName@@ + + # # Allow remote server configuration reports, with the URL of # http://servername/server-info (requires that mod_info.c be loaded). # Change the ".your-domain.com" to match your domain to enable. # -# -#SetHandler server-info -#Order deny,allow -#Deny from all -#Allow from .@@DomainName@@ -# + + +SetHandler server-info +Order deny,allow +Deny from all +Allow from .@@DomainName@@ + + # # Proxy Server directives. Uncomment the following lines to --- httpd-std.conf.in.orig Sat Jun 15 09:21:00 2002 +++ httpd-std.conf.in Fri Jun 21 14:25:03 2002 @@ -941,24 +941,28 @@ # Allow server status reports, with the URL of http://servername/server-status # Change the ".your-domain.com" to match your domain to enable. # -# -#SetHandler server-status -#Order deny,allow -#Deny from all -#Allow from .your-domain.com -# + + +SetHandler server-status +Order deny,allow +Deny from all +Allow from .your-domain.com + + # # Allow remote server configuration reports, with the URL of # http://servername/server-info (requires that mod_info.c be loaded). # Change the ".your-domain.com" to match your domain to enable. # -# -#SetHandler server-info -#Order deny,allow -#Deny from all -#Allow from .your-domain.com -# + + +SetHandler server-info +Order deny,allow +Deny from all +Allow from .your-domain.com + + # # Proxy Server directives. Uncomment the following lines to
[PATCH] Apache2 httpd.conf /2
Hi,
I've been asked now a couple of times for a configuration sample for mod_deflate; and
since mod_deflate is now a 'normal' module and no more experimental I think there
should be a sample in the httpd.conf; if you dont think so at least a sample as below
should appear in the docs to mod_deflate...
Ian, do you think the sample is ok so?
--- httpd-win.conf.orig Fri Jun 21 14:26:30 2002
+++ httpd-win.conf Fri Jun 21 14:44:40 2002
@@ -169,6 +169,7 @@
LoadModule userdir_module modules/mod_userdir.so
#LoadModule usertrack_module modules/mod_usertrack.so
#LoadModule vhost_alias_module modules/mod_vhost_alias.so
+#LoadModule deflate_module modules/mod_deflate.so
#LoadModule ssl_module modules/mod_ssl.so
#
@@ -948,3 +949,24 @@
#ErrorLog logs/dummy-host.example.com-error_log
#CustomLog logs/dummy-host.example.com-access_log common
#
+
+#
+# Configuration for mod_deflate
+
+# DeflateFilterNote - Set a note to report on compression ratio
+DeflateFilterNote deflate_ratio
+LogFormat "%h %l %u %t \"%r\" %>s %b mod_deflate: %{deflate_ratio}n pct."
+common_with_deflate_info
+CustomLog logs/deflate.log common_with_deflate_info
+# Set the Deflate window size (1-15)
+DeflateWindowSize 10
+# Set the Deflate Memory Level (1-9)
+DeflateMemLevel 6
+# Here is an example of enabling compression for the Apache documentation:
+
+SetEnv gzip-only-text/html 1
+SetOutputFilter DEFLATE
+
+
+# End of mod_deflate.
+
+
--- httpd-nw.conf.orig Fri Jun 21 14:29:15 2002
+++ httpd-nw.conf Fri Jun 21 14:46:07 2002
@@ -139,6 +139,7 @@
#LoadModule unique_id_module modules/uniqueid.nlm
#LoadModule usertrack_module modules/usertrk.nlm
#LoadModule vhost_alias_module modules/vhost.nlm
+#LoadModule deflate_module modules/deflate.nlm
#
# ExtendedStatus controls whether Apache will generate "full" status
@@ -948,3 +949,24 @@
#ErrorLog logs/dummy-host.example.com-error_log
#CustomLog logs/dummy-host.example.com-access_log common
#
+
+#
+# Configuration for mod_deflate
+
+# DeflateFilterNote - Set a note to report on compression ratio
+DeflateFilterNote deflate_ratio
+LogFormat "%h %l %u %t \"%r\" %>s %b mod_deflate: %{deflate_ratio}n pct."
+common_with_deflate_info
+CustomLog logs/deflate.log common_with_deflate_info
+# Set the Deflate window size (1-15)
+DeflateWindowSize 10
+# Set the Deflate Memory Level (1-9)
+DeflateMemLevel 6
+# Here is an example of enabling compression for the Apache documentation:
+
+SetEnv gzip-only-text/html 1
+SetOutputFilter DEFLATE
+
+
+# End of mod_deflate.
+
+
httpd-win.conf.patch-deflate
Description: Binary data
httpd-nw.conf.patch-deflate
Description: Binary data
[PATCH] Apache2 httpd.conf
Hi, can we apply this simple patch so that we dont have to always uncomment 12 lines for getting mod_info / mod_status working? thanks! --- httpd-win.conf.orig Thu Jun 13 20:39:04 2002 +++ httpd-win.conf Fri Jun 21 14:26:30 2002 @@ -850,24 +850,28 @@ # Allow server status reports, with the URL of http://servername/server-status # Change the ".@@DomainName@@" to match your domain to enable. # -# -#SetHandler server-status -#Order deny,allow -#Deny from all -#Allow from .@@DomainName@@ -# + + +SetHandler server-status +Order deny,allow +Deny from all +Allow from .@@DomainName@@ + + # # Allow remote server configuration reports, with the URL of # http://servername/server-info (requires that mod_info.c be loaded). # Change the ".your-domain.com" to match your domain to enable. # -# -#SetHandler server-info -#Order deny,allow -#Deny from all -#Allow from .@@DomainName@@ -# + + +SetHandler server-info +Order deny,allow +Deny from all +Allow from .@@DomainName@@ + + # # Proxy Server directives. Uncomment the following lines to --- httpd-std.conf.in.orig Sat Jun 15 09:21:00 2002 +++ httpd-std.conf.in Fri Jun 21 14:25:03 2002 @@ -941,24 +941,28 @@ # Allow server status reports, with the URL of http://servername/server-status # Change the ".your-domain.com" to match your domain to enable. # -# -#SetHandler server-status -#Order deny,allow -#Deny from all -#Allow from .your-domain.com -# + + +SetHandler server-status +Order deny,allow +Deny from all +Allow from .your-domain.com + + # # Allow remote server configuration reports, with the URL of # http://servername/server-info (requires that mod_info.c be loaded). # Change the ".your-domain.com" to match your domain to enable. # -# -#SetHandler server-info -#Order deny,allow -#Deny from all -#Allow from .your-domain.com -# + + +SetHandler server-info +Order deny,allow +Deny from all +Allow from .your-domain.com + + # # Proxy Server directives. Uncomment the following lines to httpd-win-nw.conf.patch Description: Binary data httpd-std.conf.in.patch Description: Binary data
