Search results

https://www.litespeedtech.com/packages/5.0/lsws-5.3-std-x86_64-linux.tar.gz is 404, i386 is not (but useless). End of the road for standard ? :( I like litespeed for personal use but spending 250$+50/year is a bit much... Last I tried openlitespeed it didn't work that well either.

I guess 32bit binaries are gone ? https://www.litespeedtech.com/packages/5.0/lsws-5.3-std-i386-linux.tar.gz is missing lshttpd :D

Hey, always an excellent support, problem solved with latest build, thank you!

thanks mistwang, ticket opened.

Hello, litespeed (5.2.3 on linux x86 std) process is using 100% cpu whenever I try to upload a file to a php7 (ubuntu 16.04) handler through fpm. I will try to switch to lsapi but I was wondering if it was considered a non issue since unsupported or a bug to be squashed ? thanks.

Hi, I recently upgraded my server to Ubuntu 16.04LTS and switched php to fastcgi+fpm, being tired of compiling lsapi manually for each security release. Everything works but sometimes software using header() replies cause a premature end of response header / abort request..., code: 4 and I can't...

As far as I can tell it's not on 5.0.1 standard, thanks for hinting me to gzip though, turning it off is a relief! Let's wait for 5.0.2 :)

Hrm, I need help: the following suite isn't giving the expected result with 4.2.5: ECDH+AES256: DH+AES256: DH+AES128: RC4-SHA: !aNULL DH ciphers are being ignored, along with ECDHE-ECDSA. openssl ciphers -v 'ECDH+AES256:DH+AES256:DH+AES128:RC4-SHA:!aNULL' ECDHE-RSA-AES256-GCM-SHA384...

Nice! I didn't notice that feature, you made my day :D

What about real life tests? No browser supports AES128-GCM-SHA256 and since it is below TLS_RSA_WITH_RC4_128_SHA on the cipher list it won't get picked anyway. Not trying to be picky but while we are at improving the cipher list...

Indeed, security comes at a cost, which could be user-selectable... like all other web servers allowing cipher-list tuning. By the way, the comment on AESNI going to waste still stands (all browsers using RSA with current build).

Great, much better! Now if ciphers could be sorted in strength (or offering an option to toggle @strength or @speed), as TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA should be above TLS_RSA* to have a chance to get picked by IE. Almost there 8) edit: actually TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA should be...

Thank you. Now the only thing missing is being able to tune it with cipher lists, as the hardcoded one doesn't include ECDHE ciphers and TLS_RSA_WITH_RC4_128_SHA being second on the offered list it gets chosen by all browsers but one, IE11 (see www.ssllabs.com/ssltest). edit: AESNI is useless...

Depending on how far 5.0 is, a 4.2.5 would make sense. Count me in :)

And now? Defaulting to TLS_RSA_WITH_RC4_128_SHA is not exactly HIGH as far as ciphers are concerned (although that's what I selected).

I did, let me know when you are done :)

Because you don't have lsapi packages for Ubuntu? I did use lsapi with previous versions and went through the pain of compiling the package, but it is not practical for everyday's use with security fixes being pushed quite often. And since I am not concerned by performance issues and php-fpm is...

Done. it loops on 2012-08-01 13:10:30.220 [DEBUG] EdStream::handleEvent(), fd: 16, event: 4 2012-08-01 13:10:30.220 [DEBUG] EdStream::handleEvent(), fd: 16, event: 4 2012-08-01 13:10:30.220 [DEBUG] EdStream::handleEvent(), fd: 16, event: 4 2012-08-01 13:10:30.220 [DEBUG]...

Actually, it is fastcgi/php-fpm, does it still apply?

Hi, I get this issue with lsws 4.1.x (up to .13, .11 included), on lsws standard on x64 (ubuntu 11.10), with php-fpm 5.3.6 tweaked (upload size, max body size, uploadprogress), running wordpress 3.4.1. Any idea on how to get around this issue? while the stall happens lshttpd is using 100% cpu...