4.0 road map

[mistwang]

We have been working on 4.0 feature for a while, the first public beta will be available soon. The follow main feature has been planed

• squid like disk cache (almost done, will be availabe in Beta1 release)
• SSI support (due in beta 2)
• python support with our own python LSAPI module
• ASP.NET support with our own Mono LSAPI module
• mod_security 2.0 rule parser
• Improve real-time status report
• Improve server scalability for mass hosting using control panels
• Server performance fine tuning
• native upload progress bar support, compatible with all existing non-scalable implemenation
• option to backup and version control configuration file.
• mod_macro support

If you have suggestion on new feature, please let us know.

Stay tuned.

[anewday]

Improve real-time status report

Cool, my suggestion made it to the road map. I hope it will be as good as lighttpd server status page.

How about limit number of concurrent connectons from an IP based on filetype on a vhost level and with proxy detection? Also, a whitelist to exempt certain IPs. This would come in handy for download servers where it could limit download accelerators from overloading the server.

[mistwang]

How about limit number of concurrent connectons from an IP based on filetype on a vhost level and with proxy detection? Also, a whitelist to exempt certain IPs. This would come in handy for download servers where it could limit download accelerators from overloading the server.

We do the connection limit at IP level with proxy detection now, it should be good enough for limiting download accelerators.

[embed]

One useful feature that I wouldn't mind having is the possibility to define request filter rules that work on the response.

In particular the possibility to block pages that contain sensitive information.
In ModSecurity it is possible to do that with something like this:

ModSecurity 2.5.1:
SecRule RESPONSE_BODY "ODBC Error Code"

ModSecurity 1.9:
SecFilterSelective "ODBC Error Code" OUTPUT

[IrPr]

Originally Posted by anewday

Cool, my suggestion made it to the road map. I hope it will be as good as lighttpd server status page.

There are a lot of advantages in performances and scability with LSWS but one of the most disadvantages is poor server status againts another webservers
Apache has a server-status with minimal reports but lighttpd's server-status is great!

I would strongly suggest Server-status feature which has a lot of requests

Originally Posted by anewday

How about limit number of concurrent connectons from an IP based on filetype on a vhost level and with proxy detection? Also, a whitelist to exempt certain IPs. This would come in handy for download servers where it could limit download accelerators from overloading the server.

Another requested feature is improved BW throtteling options for static files such as mod_limitipconn for apache which supports FILE TYPE, MIME TYPE and DIRECTORY
Or at least same feature per VHost not globally
my download servers got overloaded at every peak without these limits! i cant limit max connections globally because of my another customers

That would be really great to have this features in LSWS 4 and i cant wait

Thanks goes to LSWS Developers, Specially George

[IrPr]

Any timeline for 4.0 release?

[d3vnul]

Originally Posted by IrPr

Any timeline for 4.0 release?

I second that, it's been quite a gooood time since the development for 4.0 started.

[anewday]

Really looking forward to this.

[Tony]

Originally Posted by IrPr

There are a lot of advantages in performances and scability with LSWS but one of the most disadvantages is poor server status againts another webservers
Apache has a server-status with minimal reports but lighttpd's server-status is great!

I would strongly suggest Server-status feature which has a lot of requests

I have to agree with you there. The latest beta has improved the status page quite a bit it's a lot easier to use now. But the one thing that is lacking is a quick way to see where all the requests are going to. It's great there are 5 requests to domain.com but where on domain.com?

It would also be neat if somehow a basic server-status could match up with the control panels way of showing it. That way in cPanel for example the apache status link still shows something but this time coming from litespeed. But I don't know how feasible that would be but then it would make it really a drop in.


Still love litespeed a lot more than Apache though

[anewday]

A better status page has been requested many times on this forum. I would also like the Apache Status page in WHM to be integrated with Litespeed's.