Search results

"@inspectFile" operator is not supported now.

what secfilter rule you used? it should work, it can match pattern against any http request header.

"Allow Override" has no effect on vhosts configured via httpd.conf, you have do it in Apache configuration form httpd.conf.

When I visit vbseo.com, the request header is like cookie value is interesting, could be used as signature for guest user if all vbseo enabled forums have this cookie. The rewrite rule should only test request cookies indicating a guest visitor,then mark it as cacheable.

For rewrite rule problem. just enable rewrite log, for vhost from httpd.conf, use directive "RewriteLogLevel 9" for that vhost, then check rewrite related log entries in the error log.

It is a mystery now why PHP crash with large cookie size. If you could create a simple test script to trigger it, we would like to investigate it in our lab.

If Apache/PHP crash, user only got a blank page.different symptom. Likely a PHP internal issue as LSAPI does not deal with cookies at all.

try "force reinstall" from web console.

got it. support for SecMarker and skipAfter action is required, should be easy to implement. We do assume rule ID is numeric though, all examples given in modsec document are integers. We are adding more features for our 4.1 release to improve the compatibility with modsec 2.5, however, there...

you missed the script handler configuration for ".php".

You can create your own custom index script, then set http://www.litespeedtech.com/docs/webserver/config/general/#autoIndexURI at server or vhost level.

Are you talking about "chain" and "skip" actions? those actions are supported currently. There are litespeed users loading getroot or some other modsec rule sets. rules using regular express matching do work. It does not break LiteSpeed.

We have been adding 2.5 features into our modsec engine, @pm, @pmFromFile are supported in our 4.1RC4 release already. We will continue adding more features based on popularity and importance.

Litepspeed Cache uses rewrite rule to fine tune the cache policy, only cache pages that is safe to be cached. It can apply to IP.Board.

change configuration from '--with-mysql=shared,/usr' to '--with-mysql=/usr', then rebuild PHP.

You can move "serial.no", "license.key" to parent directory, in "lsws/", instead of "lsws/conf", it should work fine.

If you use symbolic link, you have to link the "conf" directory. LiteSpeed always create new configuration file, then rename, it is to prevent corrupting current configuration when out of disk space.

Using "/usr" is correct, you can ignore "include", "lib64". So, you have built your binary correctly, just did not load the shared modules. Copy over php.ini used by Apache PHP to /usr/local/lsws/lsphp5/lib/, should make it work.

"rpm -ql mysql-devel" to check where those files installed, if it is installed to a special directory, change your PHP configuration parameters to use that location.

"PHP suEXEC max connections: 1500" is way too high, should reduce it to 100-200 Your problem is likely because PHP script code issue, or mysql slow queries, you should try to optimize from those directions. In crease "Max connections" only mask those problems.