www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Braithwaite <...@alink.net>
Subject general/4210: Identical (same IP & port) Listen directives hose Apache
Date Wed, 07 Apr 1999 23:44:15 GMT

>Number:         4210
>Category:       general
>Synopsis:       Identical (same IP & port) Listen directives hose Apache
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Wed Apr  7 16:50:01 PDT 1999
>Originator:     mab@alink.net
>Release:        1.3.1
BSD/OS 4.0 through M400-022; standard compiler
Let's say I do

	Listen foo.alink.net:80
	Listen bar.alink.net:80

where foo and bar are CNAMEs for the same thing.  This screws Apache up in ways
that, I'm afraid, are a little hard to characterize.  I get a lot of these in
the log:

[Sat Apr  3 04:11:47 1999] [error] (38)Socket operation on non-socket: accept: (client socket)

and Apache was not answering on the IP and port indicated.
Two identical Listen directives should do it.
I think users should be allowed to do this.  Even if hostnames resolve to the
same IP address, having them all in httpd.conf is a useful way of indicating
what duties the machine's web server performs (where those duties correspond to

If this is not going to be allowed, though, it should fail better, perhaps by
being caught by `apachectl configtest'.

[In order for any reply to be added to the PR database, ]
[you need to include <apbugs@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]

View raw message