On 24/03/2010, at 14:43, Ryan McIntosh wrote: > Unfortunately curl and wget connect just fine - the only https clients I have > found that present an error are Firefox 3.0+ and chrome/chromium.
It may be related to keep-alive then. Neither curl, nor wget can use keep-alive between independent invocations. > I have thought about writing a selenium test to refresh FF on the home page. > I think I will do so. Please do! That'd be *pretty* useful for tracing and fixing the issue. > Some further information. The service was up and stable for over a month on > a 32-bit debian system (same version of c library and openssl). Due to > memory constraints we migrated the front end web server to a 64-bit Debian at > the beginning of February and that's about when this started happening. > Yesterday, I compiled a version of cherokee exactly the same on a 32-bit > Debian system and chrooted it on the 64-bit server. I am going to run this > cherokee binary on the 64-bit server and hopefully that alleviates the issue. > If it does, it would indicate an incompatibility with the 64-bit libc > shipping with Debian lenny. It could be, although I think it's more likely related to TLS connections being left open (because of a keep-alive request) on situations when they should had been closed. -- Octality http://www.octality.com/ _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
