Cherokee Web Server

Etienne Desautels | 11 Jun 2012 17:39

Bugs and Cherokee State


Hi,

I'm glad to read that someone (Stefan de Konink), want to give some love to the "stable" branch of Cherokee. I
was on the point of changing to something else (probably Nginx). And I'm sure I'm not the only one. The list
was mostly dead, the community seems to collapse quickly. This is bad signs for an open source project.

Here are the issues that bugs me:

1. Recently my client upgrade Firefox from 3.6 to version 10 ESR. Result: all pages of their site served
under HTTPS are a lot slower (at least 3x slower).

After a few tests the problem really seem to come from the combination of Firefox 10+, SSL/TLS and Cherokee
(1.2.101). I tried many sites that can be view in HTTPS and HTTP with Firefox 10 and Firefox 3.6 and most
sites served by Cherokee were more slow only with Firefox 10 under HTTPS. I didn't see any significant
differences with site served by other servers.

The slowness really come from the server, not the browser. If I look in Firebug on the network panel, my
typical page under HTTPS and FF10 take around 1.15 sec. to load, most of this time is waiting. Same page with
FF3.6 under HTTPS took 200 ms.

2. The Timeout settings are not respected under SSL/TLS. To whatever value I set the timeout setting
(via
general > network settings > timeout
or
vserver > behavior > restrictions > timeout),
the server always timeout after 15 sec.

It's with cherokee 1.2.101 on Ubuntu 10.04 with uwsgi (-t 600) and over SSL.

(Continue reading)

headers

Stefan de Konink | 11 Jun 2012 18:06

Re: Bugs and Cherokee State

Hi Etienne,

> The slowness really come from the server, not the browser. If I look in 
> Firebug on the network panel, my typical page under HTTPS and FF10 take 
> around 1.15 sec. to load, most of this time is waiting. Same page with 
> FF3.6 under HTTPS took 200 ms.

Could you check if the same things happens using the *latest* stable 
github version? There are quite some stability changes in so I hope it is 
actually fixed. If not, please let us know.

Stefan

headers

Stefan de Konink | 12 Jun 2012 11:02

Re: Bugs and Cherokee State

On Mon, 11 Jun 2012, Etienne Desautels wrote:

> 1. Recently my client upgrade Firefox from 3.6 to version 10 ESR. 
> Result: all pages of their site served under HTTPS are a lot slower (at 
> least 3x slower).

I have tested in Chrome with and without false-start 
(--disble-ssl-false-start) and it becomes clear that the first request in 
the keep-alive request takes about one second 'extra', the one second 
sounds like a programmed timeout to me.

Thus although we have 'fixed' the POST breakage, which is obviously a step 
in the right direction, figuring out where this one second comes from (a 
delay induced by the webserver, or a anticipation from the client on the 
webserver not doing something yet) sounds like a good thing more people 
can help with using CHEROKEE_TRACE=all.

I have asked Etienne to log a bug in the Google Bugtracker.

Stefan