Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 82569 invoked by uid 500); 30 Aug 2002 05:11:47 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 82545 invoked from network); 30 Aug 2002 05:11:46 -0000 Date: Fri, 30 Aug 2002 00:12:00 -0500 From: "jb2002@pc9.org" To: dev@httpd.apache.org Subject: Re: 2.0.40 (UNIX), mysterious SSL connections to self In-Reply-To: References: Message-ID: X-Mailer: JBMail Plus 3.1 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > I'd bet that this is idle server maintenance (taking down a child > process which isn't necessary). The non-SSL path doesn't log an error > for a dummy connect but evidently the SSL path does. > > The connect to itself isn't a bug, though it would be nice to avoid the > SSL complaints. Try swapping the order of your listen statements to see > if that gets rid of the complaints (i.e., if the dummy connect to wake > up a child is then done to the non-SSL socket). Well, incredible... that seems to have gotten rid of the errors (at least, none have appeared in 2 hours whereas usually one appears within a few minutes). I commented out the Listen 443 in ssl.conf, and instead modified httpd.conf so that it says this: Listen 443 Listen 80 i.e. Listen 443 before Listen 80 And no more complaints. Perhaps something like this should be the "recommended" configuration, or maybe if apache processed ssl.conf before httpd.conf that would accomplish the same thing? - Jem Berkes