Search results

ruid2, mpm_itk, itk has been blacklisted automatically in latest release, so you do not need to do that manually now.

Please update to the latest build mof 5.0.7, the size limit has been increased to 1MB. so the large css file will be always compressed. /usr/local/lsws/admin/misc/lsup.sh -f -v 5.0.7

That's due the file size is larger than 400KB. Litespeed does the compression in background to avoid blocking of event loop. However, the compressed file should be cached until the file has been updated or the cached copy being removed. Seems server need to constantly compress that file again...

Probably in 5.2 release which will port over the module API from OpenLiteSpeed. may start to work on it in first quarter 2016. We need to make 5.1 rock solid first.

It is going to take a while. maybe sometime the first quarter of 2016. We need to take care of 5.1 release first.

There was a bug in Header set ... env=xxxx Please update to the latest 5.0.7 build to get it fixed.

It is only available for openlitespeed right now. PageSpeed could be added to our 5.2 release as it require bigger internal changes.

Yes it should work.

We need to follow the official mod_security format, cannot add something arbitrary to the log message.

There is an option in tuning tab to turn on multi-cert support, do you have it enabled? The RSA cipher is probably added automatically to make sure the cipher is HTTP/2 ready. You may need to patch source code to turn if off if you want.

Does Apache's audit log have the GEO COUNTRY code in part A? As there is no clear definition of format of audit log part A, litespeed does not log the GEO COUNTRY code logged there. We can update our log format to include that.

The naming is important. you can use keyFile /httpd/ssl/server.key certFile /httpd/ssl/server.crt rename the rsa pair to server.key/crt. then just rename DSA pair to server.key.dsa server.crt.dsa no need to list the dsa pair in the configuration.

304 response does not have a response body.So, content-encoding header wont be there. Try a full reload. let us know the exact URL. we can test as well.

Your need to configure GeoIP database in LiteSpeed native configuration. SecGeoLookupDB does not work.

We tested it, working fine with your first configuration. Please check error log, there could be something wrong with your vhost configuration. or the listener to vhost mapping was not configured correctly. Turn on debug logging to check how the request was handled.

For Litespeed native vhost configuration, you can create a redirect context.

should work.

It could be cuased by ser's PHP code, or a PHP internal bug, either way, may not be some thing can be easily fixed by yourself.

It is from php internal.

Yes. absolutely.