Search results

rtight, it works in .htaccess, just like other rewrite rules. currently, no special response header to indicate it's from cache. however, it's easy to verify if it's from cache or not. for example, <?php header('CurrentTime: '.gmdate('D, d M Y H:i:s', time()).' GMT',true); echo...

yes, lsws can. for example, RewriteCond %{HTTP_COOKIE} username=guest RewriteRule /index.php - [E=Cache-Control:max-age=600] if uasename=guest exists in cookies, lsws cache /index.php page for 600 seconds(10 minutes). for subsequent requests: if there is uasename=guest cookie in...

to identify where the problem is, you've to give us more detail. please PM me the forum URL, to see if I can reproduce.

any issue? it's working fine now as you said.

in general the setting is ok. you can also set "Dynamic Requests/second" to 1~5, instead of 0, --- depends on what service your website provide.

please try: # BEGIN W3 Total Cache RewriteEngine On RewriteCond %{REQUEST_URI} \/$ [OR] RewriteCond %{REQUEST_URI} !(\/wp-admin\/|\/xmlrpc.php|\/wp-(app|cron|login|register).php|wp-.*\.php|index\.php) [OR] RewriteCond %{REQUEST_URI}...

for php suExec, only eAccelerator is recommended. since one php suExec process's "lifetime" is short. the web server process(litespeed) dynamically start/stop a new php process according to the traffic. the in-memory opcode cache only associated with for particular php process which only run...

there is a linux utility "logwatch", you can take a look.

can you test your app without the rewrite rule ? then can estimate the impact of rewrite rule.

right. you don't need worry about 2 or 8-CPU license much. as stated in the wiki: "For leased 1/2/4/8 cpu license, you can choose upgrade/downgrade between them. For upgrade, the system will calculate the price difference. For downgrade, you can do it at end of your current billing cycle."...

1.directly edit httpd.conf, just like apache is running 2.the trial license is full function 2-CPU license for 15 days. if you want 8-CPU license, you need upgrade. they are different price. more info please refer...

any error message in error.log or stderr.log? if your php script are fetching contents from outside URL, it may take time to finish, and that is why: can you specify how it looks like under nginx.

the reason ? what's the output of: #pstree -p |grep litespeed

please adjust AIO Block Size 1M to 2M at peak hour, to see if any difference. also, increase memory 8G-->16G, 32G etc can improve the I/O too. the linux kernel will fully use the memory, as disk cache for example. average iowait is 19.02 during peak hour --- still acceptable I think. Can any...

it's already fast enough, you can compare with other servers. if switch to SAS, it may be even faster, not bad :)

please try: replace "&key=%1" to "\%3Fkey=%1". i.e. RewriteCond %{QUERY_STRING} key=(.*) RewriteRule ^iembed\.swf...

overall average iowait only 2.14, it's very low. the value is statistics for the time since system startup (boot). to watch current iowait status: (from "man mpstat")

how about modify rewrite rule slightly: RewriteCond %{QUERY_STRING} key=(.*) RewriteRule ^iembed\.swf...

what's the IOwait value? #mpstat -P ALL

not set in WHM, but in lsws Admin Web Console: Configuration-->Server-->Tuning-->Connection Timeout (secs)