I can reproduce the problem every time. You can find the exact steps here: https://svn.mayastudios.de/fred/ticket/55#comment:4 However, since I and several other people are using the server I downgraded to Apache 2.2.11 again (with which you can't reproduce the problem). However, I could upgrade to Apache 2.2.12 for a short time so that you could reproduce the problem yourself. Just let me know when you're ready to do so (so that I can keep my server's "downtime" as short as possible). I'm in the SVN IRC chat very often (username is "Manski") so this would be a way to contact me.

On Mon, Aug 03, 2009 at 08:17:26PM +0200, Sebastian Krysmanski wrote:
> After some trial and error I found out that the problem (at least the cases
> I could reproduce) only occurs when using Apache HTTPd 2.2.12. After I
> reverted to version 2.2.11 the error was gone (but this can't be a permanent
> solution).

httpd 2.2.12 enabled the TLS SNI extension, which is undoubtedly
related. Could you file a bug against mod_ssl here:

(it is possible this bug lies anywhere between neon, OpenSSL and
mod_ssl, but we should first eliminate mod_ssl)

Do you control the server for which this bug can be reproduced? If so
it would be helpful to enable "LogLevel debug" (temporarily) in the
global server configuration, and capture complete mod_ssl debug logs
whilst the problem is reproduced.

Do you also have a precise set of steps I could follow to reproduce the
issue? Could you also find out what version of OpenSSL the server is
using?