It ought to be the best web server #81

Open
Borkason opened this Issue Mar 24, 2013 · 11 comments

Projects

None yet

1 participant

@Borkason
Member

Original author: alobbs (July 01, 2007 22:32:11)

We still have quite a few things to do in order to make Cherokee the best
web server.

Original issue: http://code.google.com/p/cherokee/issues/detail?id=1

@Borkason
Member

From alobbs on July 02, 2007 17:38:57
Changing the type, it isn't a defect but an enhancement. (I'm testing the bug
tracking system actually).

@Borkason
Member

From adef...@gmail.com on October 16, 2007 16:54:39
OK, maybe this goal will take several years :-), also because we are far away from
version 1.0.0

@Borkason
Member

From tah...@gmail.com on August 05, 2008 21:08:44
We'll get there in time :)
I'm really looking forward to the release of 0.8. At this pace we'll get to 1.0 in no
time at all.
I'm impressed so far :)

@Borkason
Member

From tah...@gmail.com on October 29, 2008 16:27:32
Just wanted to make a note...
I don't know about being the best (well, I think it is, but that is just my
opinion). But what is true is that it already is the FASTEST :)

Yeah, I know... every time we make a release (0.10 today) I get excited. Blame it
on the boogie!

@Borkason
Member

From michael....@gmail.com on August 26, 2009 10:34:20
Bestest! :-)

@Borkason
Member

From amoiz.sh...@gmail.com on March 31, 2010 11:42:09
awesome server!!!

@Borkason
Member

From anonsph...@gmail.com on July 19, 2012 02:53:58
I started to revert my servers back to apache2 and nginx. One year ago, cherokee was a really interesting project, but as even critical, high and medium bugs are not fixed anymore, it makes no sense to recommend or even use it further in a production environment.

Last update is now 8 month old and your webserver has just become unusable, especially for the german market with > 40 % firefox users. There are big lags since FF10, there are ssl problems, there are still problems with cookies > 4kb and after using cherokee for one and a half year now, my personal vote has gone down from "full of expectations" to "just annoying".

Meanwhile the documentation is totally outdated, there are no new features like spdy or e. g. the accelerated upload support I suggested 1 year ago, where nobody even had the time to comment on it. I think, it does not seem as anybody is interested in making cherokee better anymore.

It makes me really sad to say it, because I was one of you biggest fans, but I think the best time for cherokee is over. Thanks for your work and bye!

@Borkason
Member

From ste...@konink.de on July 19, 2012 08:52:33
Did you see our github project?

@Borkason
Member

From anonsph...@gmail.com on July 19, 2012 10:38:04
Yes, I did.

@Borkason
Member

From ste...@konink.de on July 20, 2012 08:55:07
If you did, then your claim that the last update is 8 months can't be true. Since less than a month ago it was announced that the SSL n-1 and false-start problems were solved. I would like to point out that spdy development has started, which was also announced on the mailinglist. I have not see accelerated update methods, so could you please point me at that?

Regarding to 4kb cookies. I think such numbers are rather big, especially for mobile appliances. But lets see what we can do, in anyway: sending in patches or qa-tests, help more than complain.

@Borkason
Member

From anonsph...@gmail.com on July 29, 2012 14:31:20
Oh you mean qa like there => http://code.google.com/p/cherokee/issues/detail?id=27 (Github: #101) or there http://code.google.com/p/cherokee/issues/detail?id=1287 (Github: #883)? I commented and never heard of it again. The Accelerated upload support is this ticket http://code.google.com/p/cherokee/issues/detail?id=1231 (Github: #848). Also written and never heard of again. Not even, if it is interesting enough to add it on the list. Two minor bugs written weren't even confirmed.

The problem is not, that 4 kb cookies are not received or send correctly. The problem is, that if you set a cookie this size in accident the user only sees a 500 message and will never come back. If the SSL problems are fixed, why didn't you release a new version? The last official release is 8 month old. And if you think, the new version wasn't tested enough … worst than broken is impossible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment