Search results

So did you update the conf and restart it? I just checked, it seems the first page is not gzipped and other css and js files are all gzipped.

Just there. "Server Configuration > Tuning"

I visited and it is not gzipped. Can you tune on the gzip so that I can look at the content if there is any problem?

Can you give me your site URL? I can have a look if request gzip and what will return.

I may not understand you well. The gzip compress is only for the response body, not for the header itself.

The best choice is you download 1.4.40 pre-built package, it already have the binaries and you needn't to download any openssl version for compiling.

Oh, yes. We created static linked binary since now. It can run on all Linux 64 bit platform, and this is the difference.

Yes. Keep it. It is very close to the next release version.

Can you download http://104.248.3.50/openlitespeed-1.5.0.tgz and extract to test the binary bin/openlitespeed? Make a copy of your current binary first. Just test if the bug is fixed or not. Thanks.

This may be a bug that we fixed in 1.4.40. We will release a new v1.5.0 RC soon and it will contains the same fix.

I see and we will fix it soon. Thanks.

Can you give me more info about the rewrite rule? Such as is it in .htaccess and which version of 1.4 and which version of 1.5. We fixed a rewrite rule bug in 1.4.40 which should still be in 1.5rc version.

So you should have install yajl and yajl-devel when build the libarary libmodsecurity.a? After the make, it should give you a result of which module is enabled or disabled. If you find yajl is enabled and now, you get such an error, maybe it is a bug of libmodsecurity, we need to tell them.

Since our Makefile.f does not have the symbol linked, maybe you can try to add "-lyajl -lxml2 " to LDFLAGS and re-make the .so file if you have the dependency libraries installed. This way is try to fix this issue. Otherwise, you can just disbale this module in the webAdmin and it will not...

OK. The YAJL is an optional dependency, I do not know why it become a must and why check this symbol. Will reply you later. Please just disable the module right now. Thanks. David

It seems the module loaded correctly but it runs failed and cause server crash. If disable this module, server should be up. It maybe because the server code and module code do not match. I tested mod_security.so, and never see such issue.

It seems something wrong while php is serving this file. Can you change the log level to DEBUG HIGH and check if any errors relative with php in you log while reproducing such an issue?

It seems openlitespeed may have a memory leak issue. Can you check its usage of memory? If it is keep increasing, it probably is because of this issue.

1, While serving a request, if the response header says 'server can save to private cache', then the private cache function will be automatically enabled, even if it is disabled in setting. 2, While serving a request, if there is private cache saved, server will serve this request with the...

If the response header says server can save to private cache and private cache will be automatically enabled. While serving, if there is private cache, server will serve it.