apache2 default conf file contains Listen directive

Bug #1105411 reported by John Moser
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apache2 (Debian)
Fix Released
Unknown
apache2 (Ubuntu)
Invalid
Low
Unassigned

Bug Description

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.

Revision history for this message
Thomas Ward (teward) wrote :

Importance: Low.

Reason: not really a bug that prevents operation, more rather a bug that addresses minor housekeeping of the default configs.

Requested via IRC, by bluefoxxx. Processed by myself ("TheLordOfTime"):
[15:13:33] <bluefoxxx> That should be a very low importance but I can't triage my own bugs.
[15:13:45] <TheLordOfTime> triage requires bugcontrol usually, which bug?
[15:13:53] <bluefoxxx> 1105411
[15:13:58] <TheLordOfTime> LP Bug 1105411
[15:13:59] <ubot2> Launchpad bug 1105411 in apache2 (Ubuntu) "apache2 default conf file contains Listen directive" [Undecided,New] https://launchpad.net/bugs/1105411
[15:14:43] <TheLordOfTime> bugs usually need to be confirmed before we triage, but i agree on the low importance
[15:14:47] * TheLordOfTime sets the bug as Low Importance
[15:14:47] <bluefoxxx> It's low priority because it's effectively meaningless housekeeping minimizing the configuration
[15:15:06] <TheLordOfTime> agreed, which is why i set it :)

I'm not marking this as triaged, yet, as I have not confirmed this bug yet. (although a fix for this bug should be exceptionally minor)

Changed in apache2 (Ubuntu):
importance: Undecided → Low
Changed in apache2 (Debian):
status: Unknown → New
Revision history for this message
John Moser (nigelenki) wrote : Re: [Bug 1105411] Re: apache2 default conf file contains Listen directive

I think I'm completely wrong on this, my fault for doing this completely
from memory without verifying that it actually works.

The problem is more of Apache's completely unexpected behavior: it listens
on whatever port you tell it. You have only a virtual host on *:1080?
Listen 80, it comes up and listens on 80, does not serve your site. You
have multiple virtual hosts on one port, and multiple others on other
ports? You can't have multiple Listen directives on the same port, Apache
won't start.

The same information is in two places and it doesn't have to make sense.

I should have actually checked before I filed this invalid report; the
actual issue I want to report is something completely different and
upstream.

On Fri, Jan 25, 2013 at 4:22 PM, Bug Watch Updater <
<email address hidden>> wrote:

> ** Changed in: apache2 (Debian)
> Status: Unknown => New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1105411
>
> Title:
> apache2 default conf file contains Listen directive
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1105411/+subscriptions
>

Revision history for this message
Thomas Ward (teward) wrote :

Marked invalid per email response from original poster.

Changed in apache2 (Ubuntu):
status: New → Invalid
Changed in apache2 (Debian):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.