Package: apache2-common
Version: 2.0.53-5
Severity: normal
*** Please type your report below this line *** According to
http://httpd.apache.org/docs-2.0/suexec.html#install (Setting paranoid
permissions section), the suexec script should be owned by group
www-data and have 4750 permissions, as a s
Package: apache2-common
Version: 2.0.53-4
Severity: important
Apache is occasionally returning 304 responses to standard HTTP
requests. As I understand it, a 304 should only be returned in response
to a conditional GET. However, I am seeing it in response to normal GETs.
For example, I ran the fol
Package: apache2-common
Version: 2.0.52-3
Severity: wishlist
ssl.conf should contain the line:
SSLCertificateFile /etc/apache2/ssl/apache.pem
With that in place, SSLEngine on would be the only thing required to
turn SSL on without where desired.
Charles
-- System Information:
Debian Release
Package: apache2-common
Version: 2.0.52-3
Followup-For: Bug #267477
The following /etc/apache2/sites-available/ssl is sufficient to get an
HTTPS server running:
# add "Listen 443" to ports.conf
SSLEngine on
# generate with apache2-ssl-certificate
SSLCertificateFile /etc/apache2/
Package: apache2-common
Version: 2.0.52-3
Severity: wishlist
I have a recommendations for apache2-ssl-certificate:
Use a configuration file, perhaps /etc/apache2/ssl/apache.cnf, to
store all of the information that the script currently prompts for. This
simplifies the process of regenerating a ne
Package: apache2-common
Version: 2.0.52-3
Severity: wishlist
It would be most helpful to have a README file in /etc/apace2/ssl
explaining that apache2-ssl-certificate could be used to generated the
necessary certificates.
Charles
-- System Information:
Debian Release: 3.1
APT prefers testing
Package: apache2-common
Version: 2.0.52-3
Severity: wishlist
The whole mod_vhost_alias framework in apache2 is very cool and very
helpful in hosting large numbers of sites. The one big configuration
paramater that I find missing is:
VirtualServerAdmin
This could be used like VirtualDocumentR
cache.conf should also provide a default CacheRoot (perhaps
/var/cache/apache2/disk_cache). Further, the CacheRoot directory should
be created and assigned www-data ownership to allow immediate usage once
CacheEnable is set to disk.
Charles
--
Thrifty jars for
Stay at homes
Handy tubes
For him
W
Package: apache2-common
Version: 2.0.52-1
Severity: minor
Inasmuch as mod_cache requires the CacheEnable directive in order to
enable cacheing, it would be most helpful to provide a cache.conf that
had a simple (perhaps commented out) CacheEnable example with a brief
description of the CacheEnable
> You've described perfectly the situation where you do not have a
> NameVirtualHost line that does not match your VirtualHost stanzas.
> eg:
> NameVirtualHost *:80
>
>
>
>
> Apache will produce a warning in that case.
> I have many hundred systems all using VirtualHost * succesfully with
Package: apache2-mpm-perchild
Version: 2.0.48-7
Severity: normal
When I query http://127.0.0.1/server-status?auto, I always get 0 for
BusyWorkers and IdleWorkers:
BusyWorkers: 0
IdleWorkers: 0
I assume that at least one of these should have a non-zero value.
Charles
-- System Information:
Debi
Package: apache2-mpm-perchild
Severity: normal
Whenever I run "apache2ctl graceful", which I have understood to be the
cleanest way to restart apache2, the number of apache2 threads doubles.
It appears that all of the old ones remain, and the same number of new
ones are created. I don't know if th
Package: apache2-common
Severity: normal
The [1][2]Apache documentation indicates that when using
NameVirtualHost, the VirtualHost directive should use * (as opposed to
_default_) to match all IP addresses. However my experimentation has
demonstrated that if I have multiple VirtualHost entries, wi
Package: apache2-common
Severity: normal
The contents of the default ssl.conf are not sufficient to allow the
establishment of an https connection.
/usr/share/doc/apache2/examples/ssl.conf.gz contains a very near
complete sample ssl.conf, and requires only minimal changes to make it
functional. It
> > > This is because your DNS is broken.
> >
> > In what way do you supsect that my DNS is broken? I am running under
> > usermodelinux, so that may effect the order that certain things happen.
>
> I'm not the OP but 'broken DNS' was my first guess too. Your server
> probably tries to resolve i
> > Every time my webserver reboots, apache2-mpm-perchild takes around 3
> > minutes to startup. For a long time I thought it was hanging, and
> > would simply kill it, but today I realized that after waiting long
> > enough it would eventually start (at least some of the time). I
> > realize that
Package: apache2-mpm-perchild
Severity: normal
Every time my webserver reboots, apache2-mpm-perchild takes around 3
minutes to startup. For a long time I thought it was hanging, and would
simply kill it, but today I realized that after waiting long enough it
would eventually start (at least some o
Package: apache2-mpm-worker
Severity: minor
The current apache2-mpm-worker description is misleading. It mentions
that it "It is considerably faster than the traditional model, but has
not currently received as much testing." This certainly used to be the
case, but no longer accurately reflects th
Package: apache2-mpm-prefork
Severity: minor
The current description of the apache2-mpm-prefork Debian package is
incomplete, and insufficient to allow a user to evaluate its utility
without consulting Apache's documentation themselves. Here is a good
paragraphs I found in Apache's documentation t
Package: apache2-mpm-threadpool
Severity: minor
The current apache2-mpm-threadpool description is misleading. It
metnions that it is an experimental implementation. However it also
claims that "It is somewhat faster and less CPU intensive than the
worker model." According to the [1]most recent apa
I posted this to debian-policy on 2 Feb 2004, but based on the response
I got there, and potentially related thread on a new web server policy
here, I thought I would also post to debian-apache:
Please let me know if this should be posted elsewhere. I am not a Debian
developper, but I see an issu
21 matches
Mail list logo
