Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (athena.apache.org: domain of info@apachelounge.com
 designates 85.223.52.177 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
	s=default; d=apachelounge.com;
	h=Subject:From:Date;
	b=IpaLCOXnqFS4EufwwcuQe8wW9l9BGgFroTrpXZjJLI4hE+DrbdEOF+wb4oe0kelcF+6xJ1cqRPkuM6eQzs49wolRVZzBWkXHDytRKoKGJ7KTMCA0L615Tz+Fmnn2HOIv;
Subject: Re: SSL and windows with AcceptFilter https none
References: <4F1595B9.50502@primary.net>
From: Steffen <info@apachelounge.com>
Content-Type: text/plain;
	charset=us-ascii
In-Reply-To: <4F1595B9.50502@primary.net>
Message-Id: <32B53C9C-C0C1-4D2A-AFB3-E582767D069A@apachelounge.com>
Date: Tue, 17 Jan 2012 19:25:36 +0000
To: "dev@httpd.apache.org" <dev@httpd.apache.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)

It is line with our reports. Thanks, and this confirms again there is some b=
roken serious.=20

For me a showstopper 2.4, tons of win users going to deal with this.=20

Work around is to use 2.2.21 SSL-only and minimal config in front of 2.4.=20=


Op 17 jan. 2012 om 15:37 heeft Daniel Ruggeri <DRuggeri@primary.net> het vol=
gende geschreven:

> All;
>   I have submitted PR 52476 to track and document this bug. I've
> uploaded the logs from my tests where I was able to duplicate the problem.=

> http://people.apache.org/~druggeri/logs/WinSSL/
>=20
>   Initially I was just setting up my testbed and hitting 127.0.0.1 to
> make sure the small LWP script can duplicate the problem and help track
> it down... it was trival to reproduce the bug on this Winsows 7 x64
> installation. Since I was able to reproduce quickly, I never got past
> testing on local IP's, though this should suffice since it's technically
> running through the TCP stack just as well.
>=20
>   I was able to reproduce inconsistently in Firefox 8.0.1 and IE 8
> after enabling AcceptFilter https none. I was able to consistently
> reproduce the error with openssl-based clients (LWP and openssl
> s_client). The common error across all clients is a complaint with the
> ClientHello message. I was not able to find a failure where partial
> content was served - it was all or nothing for me at an SSL connection
> level.
>=20
>   I don't have the expertise to dig into this one, but since several
> folks have been unable to reproduce the problem, I'll be happy to serve
> as a testing ground.
>=20
> --=20
> Daniel Ruggeri
>=20