All php scripts include code like this to redirect users to mobile subdomain of site, if mobile device detected. (...
im working with litespeed private and public cache with good results, but there is a problem with redirects.
Using an included...
Step 3 : Preparing for building PHP 5.3.18 Binary
Stopped due to Error. Please manually fix it.
**MAIN_STATUS** retrieved from...
Is possible use cache with .shtml files?
tcp_tw_recycle was actually set a 1
doing some tests, disabling litespeed smart keep alive seems to lower time_wait connections to 9.000-10.000
there aren't any ip with more than 10 or 15 time out connections, there are thousands of ips with about 5-15 connections.
disabling tcp_syncookies, i get dropped...
under litespeed server I'm getting these errors at /var/log/messages :
Oct 10 19:09:27 01 kernel: TCP: Possible SYN flooding on port...
no problems at all with 4.0.20, dir /tmp/ is at 15% usage all time and doesn't grow.
Just forced-install upgrade again to 4.1.2 build 29 Jul, will...
will wait one day with 4.0.20 to be sure tmp problem is related to lsws, and then force reinstall to latest 4.1.2 (i was using version downloaded day...
but was taking only 50-70mb max, with clean cron running.
Currently with 4.0.20 and zero config changes no problem at moment.
still with problems:
Filesystem Size Used Avail Use% Mounted on
/dev/sda8 996M 866M 79M 92% /tmp
# service lsws restart...
after upgrading to from 4.0.20 to 4.1.2, /tmp/ directory begins to grow (1gb), but do not get to show any files that occupy that space. Restarting...
After upgrading from 4.0.20 to 4.1.2, log is full of:
... "gzipped, response body size is 20, no cache."
What do these log entries mean?
Testing LiteSpeed 4.1.1 im getting these errors:
2011-05-22 22:47:11.252 NOTICE [.46.121] bot detected, close connection!...
Smart Keep-Alive No
Document Path: /test1.css
Document Length: 13 bytes
Concurrency Level: 100
Time taken for tests: 41.586...
Smart Keep-Alive ON, file: test1.css
Concurrency Level: 100
Time taken for tests: 38.232 seconds
Complete requests: 1000000
no effect changing Max Keep-Alive Requests from 1.000 to 10.000, same result.
But got it changing Smart Keep-Alive from Yes to No...
Separate names with a comma.