Search results

So how about to set the context to /?

Thank you. I will fix that.

Good to know. Thanks.

Yes, we know the reason. You may set `httpdworkers 2` in the server conf file and set less php CHILDREN(such as 5) in the ENV setting, also you can set less `max connection` . We will release 1.5.5-2 soon, which should save a lot resource.

Good. Thank you.

I installed 1.4.50 freshly and check the webAdmin, it seems everything is good. Did you update form some other version?

I think you an do this way. In the Vhost conf file rewrite block, add a rule to set the env, such as my test case rewrite { enable 1 logLevel 9 RewriteRule ^(.*) $1 [E=SERVER_ROOT:80] }

I will check and will update you. Thanks.

Oh, the notice is just a notice, it will download the package file. I will fix the notice in the next release. But you still need to download it from our site or GitHub and upgrade yourself.

OK. This is a bug and we can fix it in the next release. Thank you

OK. Sorry for my question, because I got some tickets as I just mentioned and they are the same result as your issue. So, yes, do some tuning of the php children and max connection. Please let us know if it is fixed or not.

I think you are using DA+OLS+CL, if yes, please update the `httpdworkers 2`, lsphp maxConnection to 10, ENV CHILDREN to 5, or ask DA team. Thanks.

Sorry. I do not use Google Load Balancer, so I do not know what exact issue is for openlitespeed. can you give me more info, such as a what request should return 200, but openlitespeed response a non-200 error code? For the healthy status about google, I think I don't know much.

1.5.4 contains all changes and new features and also has more bugs fixing than 1.4.49. Yes, I suggest to use 1.5.4.

Sorry I missed this message. And I just released 1.5.4 without this bug fixed. I am debug it now, will update you once I have it fixed. Thanks for your report.

Yes, please give us the link which file is increased while using cache. Thanks.

Good. Thank you reported me for this hidden bug.:D

I fixed a bug about the auto load .htaccess, can you still comment out the context dir2 block to check if the new 1.4.50 will work. #context /dir1/dir2 { #allowBrowse 1 #} Command is still /usr/local/lsws/admin/misc/testbeta.sh 1.4.50 Thanks. David

I mean it should be auto created when first time access a file inside dir2, but not at the beginning time. I will do more testing to make it work. BTW what type of file you are accessing in dir2?

If you can set debug log to debug errorlog logs/error.log { logLevel DEBUG debugLevel 10 rollingSize 10M enableStderrLog 1 } You may see the context of .../dir2/ will be auto created when first time access a file inside, and you may see log...