Re: Bug#234650: Looks like version bit rot
On Wed, 25 Feb 2004, Phil Karn wrote:
> It seems that things must have changed just enough in apache-ssl for my
> previous httpd.conf file to stop working.
What exactly? This statement is way too generig for me to understand if
there is a problem and where is located.
> In the process I discovered some changes in the currently distributed
> httpd.conf file that may break existing practices. For example, aliases
> are provided that remap /icons/ and /images/ to directories under
> /usr/share; this will break web pages that have their own images and
> icons directories. These should probably be disabled by default.
Configurations are provided as examples. They cannot fit all users. It is
simply impossible. The aliases in the examples are there to match FHS. If
you use a different setup it is your responsability to change them.
(considering that you have reinstalled from scratch)
On upgrades these Aliases are not modified and
/etc/apache-ssl/suggested_correction will indicate that there is a
different between the defaults and your custom setup.
> Other changes are problematical since they may also break existing
> practice, but a case can be made for them because of increased default
> security. E.g., the currently distributed httpd.conf file disables the
> generation of directory listings. I'm not sure if this should be
> considered a bug or not.
You get promped for the list of modules that you want to load and dir
listing is enabled. Still your responsability to configure the modules you
need. We cannot guess them and neither we want to enable all of them by
default like other distros do.
Fabio
--
<user> fajita: step one
<fajita> Whatever the problem, step one is always to look in the error log.
<user> fajita: step two
<fajita> When in danger or in doubt, step two is to scream and shout.
Reply to: