Search results

It should have a log message at NOTICE level "Start to clean up cache directory."

It was called by LSWS server daemon when server check for new update. So, you should let LSWS check for update daily instead of monthly in order for daily cleanup.

That could be the problem with our SSI implementation, the SSI engine does expect valid response headers, headers will be stripped. Not sure how Apache handle this.

Does URL "/cgi-bin/blah.cgi" work when you access it directly? file "cgi-bin/blah.cgi" should be relative to the shtml including it.

Maybe it is a different issue. Can you give us detailed test case?

What do you mean "temporary URLs"? Just curious.

just switch back to apache, access a web site, check the entries logged by Apache. it should be something like "<time_in_seconds> <bytes> ."

Then open one up, check the content, see if it log traffic in correct format. switch between Apache and LSWS, and compare.

No, it does not work. Only SSI (shtml) works.

Is that from /usr/local/lsws/fcgi-bin/lsphp5 -i Apache PHP may use different php.ini.

I think you did not put php.ini in the right directory, check the phpinfo() output.

Under what condition? Request body could be huge, LSWS does not log request body. The most detailed request logging is in the mod_security audit log file. If you want to check the request detail, you can try "tcpdump".

Please check the bytes_log file under /usr/local/apache/domlogs/, see if it grow when you access a web site hosted.

It calls lsws/admin/misc/cleancache.sh once a day. The behavior can be customized via the shell script. Default is to remove file more than one day old based on modified time. Can be changed to based on last access time, but some system may use "noatime" option when mount the partition.

LiteSpeed has internal logic to uncompress upstream compressed content if client does not accept gzip compression. It is a feature, not a bug, and there is no way to turn it off.

add another rewrite rule RewriteRule ^$ index.html above

http://www.litespeedtech.com/docs/webserver/config/security/#accessControl_allow

No, it control the server cache behavior. You can configure LSWS to use cached page by default, and turn off cache with rewrite rule when a page should not be cached. Maybe it is not exactly what you want, I think we probably need to add a special "Cache-control" directive to tell LSWS when...

Please download and try 4.0.16 release package, it should take care of the signal 9 issue. Will announce it tomorrow.

We will have the official release build 1 ready tonight.