Your message dated Fri, 25 Jan 2013 23:29:13 +0100
with message-id <[email protected]>
and subject line Re: Bug#698967: apache2 default conf file contains Listen
directive
has caused the Debian Bug report #698967,
regarding apache2 default conf file contains Listen directive
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
698967: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698967
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: apache2
Version: 2.2.22-12
Severity: minor
This was originally reported in Ubuntu at
https://bugs.launchpad.net/bugs/1105411
This is the content of the bug as it exists in Ubuntu's bug tracker on
Launchpad:
> The default Apache 2 config file /etc/apache2/ports.conf contains a Listen
> directive.
>
> This directive is extraneous and unnecessary: The default configuration
> includes a VirtualHost that listens on Port 80. SSL configurations listen
> on Port 443. Removing the global Listen directives does not change this
> behavior; however if the default site is removed or moved to another port,
> Apache continues to listen on that port. For example, if Apache listens on
> Port 80 and you change the default site to listen on port 1080, Apache will
> listen on Port 80 and Port 1080 due to the Listen directive in ports.conf.
>
> By removing or commenting the Listen directive, Apache will no longer
> listen on Port 80 if no VirtualHost exists that specifies Port 80. This
> reduces the number of open ports, and leaves Port 80 open for other
> applications.
>
> Leaving the Listen directive in ports.conf as-is is not particularly
> harmful; it does however lead to minor, momentary confusion or excessive
> open ports when unfamiliar users configure Apache in exotic ways. As it is
> unnecessary, it should be disabled.
>
--- End Message ---
--- Begin Message ---
tags 698967 + wontfix
thanks
On 25.01.2013 23:21, Thomas Ward wrote:
> Therefore, while Debian is free to mark this however it wishes, I would
> suggest marking it as the equivalent to Launchpad's "Invalid" or "Not a
> Bug" status.
Will do. Thanks for the update.
--
with kind regards,
Arno Töll
IRC: daemonkeeper on Freenode/OFTC
GnuPG Key-ID: 0x9D80F36D
signature.asc
Description: OpenPGP digital signature
--- End Message ---
