Return-Path: 
 <users-return-102570-apmail-httpd-users-archive=httpd.apache.org@httpd.apache.org>
X-Original-To: apmail-httpd-users-archive@www.apache.org
Delivered-To: apmail-httpd-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 9378197E3
	for <apmail-httpd-users-archive@www.apache.org>;
 Fri, 17 Feb 2012 21:31:03 +0000 (UTC)
Received: (qmail 61257 invoked by uid 500); 17 Feb 2012 21:31:00 -0000
Delivered-To: apmail-httpd-users-archive@httpd.apache.org
Received: (qmail 61216 invoked by uid 500); 17 Feb 2012 21:31:00 -0000
Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
list-help: <mailto:users-help@httpd.apache.org>
list-unsubscribe: <mailto:users-unsubscribe@httpd.apache.org>
List-Post: <mailto:users@httpd.apache.org>
List-Id: <users.httpd.apache.org>
Delivered-To: mailing list users@httpd.apache.org
Received: (qmail 61206 invoked by uid 99); 17 Feb 2012 21:31:00 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Feb 2012 21:31:00 +0000
X-ASF-Spam-Status: No, hits=2.2 required=5.0
	tests=HTML_MESSAGE,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of prvs=13947c6832=kmknox@aep.com
 designates 167.239.223.107 as permitted sender)
Received: from [167.239.223.107] (HELO mail5.aep.com) (167.239.223.107)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Feb 2012 21:30:54 +0000
Received: from pps.filterd (mail5 [127.0.0.1])
	by mail5 (8.14.3/8.14.3) with SMTP id q1HLT2wi028181
	for <users@httpd.apache.org>; Fri, 17 Feb 2012 16:30:32 -0500
Received: from dsml1oh.aepsc.com ([10.97.175.1])
	by mail5.aepsc.com with ESMTP id 131xuq00bs-1
	for <users@httpd.apache.org>; Fri, 17 Feb 2012 16:30:32 -0500
In-Reply-To: 
 <OFF13B0803.6099F3A5-ON852579A7.0071063F-852579A7.00711523@aep.com>
To: users@httpd.apache.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
From: kmknox@aep.com
Message-ID: 
 <OF6C3713E5.13A0B44E-ON852579A7.00760814-852579A7.007620B3@aep.com>
Date: Fri, 17 Feb 2012 16:30:30 -0500
X-MIMETrack: Serialize by Router on DSML1OH/SERVERS/AEPIN(Release
 8.5.2FP1|November 29, 2010) at
 02/17/2012 16:30:31,
	Serialize complete at 02/17/2012 16:30:31
Content-Type: multipart/alternative;
 boundary="=_alternative 007620B2852579A7_="
X-Proofpoint-Virus-Version: vendor=fsecure
 engine=2.50.10432:5.6.7361,1.0.260,0.0.0000
 definitions=2012-02-17_04:2012-02-17,2012-02-17,1970-01-01 signatures=0
X-Virus-Checked: Checked by ClamAV on apache.org
Subject: Re: [users@httpd] Apache mod_ssl TLS channel dying in 5 seconds - how
 do I
 extend that timeout?

--=_alternative 007620B2852579A7_=
Content-Type: text/plain; charset="US-ASCII"

> 
> Eric Covener <covener@gmail.com> wrote on 02/17/2012 03:20:18 PM:
> 
> > On Fri, Feb 17, 2012 at 3:15 PM,  <kmknox@aep.com> wrote:
> > >
> > >
> > > Eric Covener <covener@gmail.com> wrote on 02/17/2012 03:04:29 PM:
> > >
> > >
> > >> On Fri, Feb 17, 2012 at 3:02 PM,  <kmknox@aep.com> wrote:
> > >> > 5 seconds later, a TLS Rec Layer-1 Encrypted Alert
> > >>
> > >> Is your base Apache KeepaliveTimeout 5 seconds and this alert is 
just
> > >> a close_notify?
> > >>
> > >
> > > We've not explicitly defined any of the keepalive settings, so they 
should
> > > default to 15 seconds, not 5, right?
> > >
> > 
> > 5 seconds in 2.2 manual and 2.2 code:
> > 
> 
> Oops. I see it now. Thanks for the correction. 

Thank you, Eric. Modifying the keepalive directly modified the 
transmission of the encrypted alert. It was indeed a keepalive terminator. 

--=_alternative 007620B2852579A7_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2><tt>&gt; <br>
&gt; Eric Covener &lt;covener@gmail.com&gt; wrote on 02/17/2012 03:20:18
PM:<br>
&gt; <br>
&gt; &gt; On Fri, Feb 17, 2012 at 3:15 PM, &nbsp;&lt;kmknox@aep.com&gt;
wrote:<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Eric Covener &lt;covener@gmail.com&gt; wrote on 02/17/2012
03:04:29 PM:<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;&gt; On Fri, Feb 17, 2012 at 3:02 PM, &nbsp;&lt;kmknox@aep.com&gt;
wrote:<br>
&gt; &gt; &gt;&gt; &gt; 5 seconds later, a TLS Rec Layer-1 Encrypted Alert<br>
&gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt;&gt; Is your base Apache KeepaliveTimeout 5 seconds and this
alert is just<br>
&gt; &gt; &gt;&gt; a close_notify?<br>
&gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; We've not explicitly defined any of the keepalive settings,
so they should<br>
&gt; &gt; &gt; default to 15 seconds, not 5, right?<br>
&gt; &gt; &gt;<br>
&gt; &gt; <br>
&gt; &gt; 5 seconds in 2.2 manual and 2.2 code:<br>
&gt; &gt; <br>
&gt; <br>
&gt; Oops. I see it now. Thanks for the correction. </tt></font>
<br>
<br><font size=2><tt>Thank you, Eric. Modifying the keepalive directly
modified the transmission of the encrypted alert. It was indeed a keepalive
terminator. </tt></font>
--=_alternative 007620B2852579A7_=--