Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 52667 invoked from network); 11 Sep 2003 10:21:02 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 11 Sep 2003 10:21:02 -0000 Received: (qmail 43306 invoked by uid 500); 11 Sep 2003 10:20:15 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 43245 invoked by uid 500); 11 Sep 2003 10:20:14 -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 43169 invoked from network); 11 Sep 2003 10:20:13 -0000 Received: from unknown (HELO localhost.localdomain) (62.212.108.2) by daedalus.apache.org with SMTP; 11 Sep 2003 10:20:13 -0000 Received: from [192.168.100.1] (auxiliance-2.clients.easynet.fr [212.180.95.194]) by localhost.localdomain (8.12.8/8.12.8) with ESMTP id h8BA16gn017206 for ; Thu, 11 Sep 2003 12:01:07 +0200 Subject: mod_ssl and slow first connection From: Apache-Mailing To: dev@httpd.apache.org Content-Type: text/plain Organization: Message-Id: <1063275620.2277.8.camel@matthieu-dev> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 11 Sep 2003 12:20:20 +0200 Content-Transfer-Encoding: 7bit X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hi, I am actually doing bench on ssl and apache 2.0.47 I can notice that the first connection is slow and the popup about the server certificate take time (~40sec) to show up. When i read the log, i can see the BIO debug say that it is waiting data. Then after the ~40 sec, it continue to process the request without error or warning messages. I changed ciphers and did more test disabling/enabling options and it's still the same. The problem is the same with IE and Netscape. I found a little patch for IE which seems to correct the bug but the problem is still here with netscape. Does somebody heard about such a problem ? Matthieu