Support

04nunhucks · #11 06-01-2011, 01:20 PM

Quote:

Originally Posted by webizen

The contact me page shows error as below. However, go back to the home page (http://shamil.la) from that page isn't slow to me. maybe it is user specific issue such as user network, etc.

LS Cache was caching that. Please check now

webizen · #12 06-01-2011, 01:41 PM

The home page doesn't seem to be served from LS cache but W3 Total Cache..

Anything served out of LS cache has "X-LiteSpeed-Cache: hit" in its response header. This one does not have such response header.

Quote:

Accept-Ranges:bytes
Cache-Control: public, must-revalidate, proxy-revalidate, max-age=-67335
Connection:close
Content-Encoding:gzip
Content-Length:3272
Content-Type:text/html; charset=UTF-8
Date:Wed, 01 Jun 2011 20:37:36 GMT
Etag:"cc8-4de58df9-0"
Expires:Wed, 01 Jun 2011 01:55:21 GMT
Last-Modified:Wed, 01 Jun 2011 00:55:21 GMT
Pragma: public
Server:LiteSpeed
Vary:Accept-Encoding
X-Powered-By:W3 Total Cache/0.9.2.2

04nunhucks · #13 06-01-2011, 01:57 PM

Quote:

Originally Posted by webizen

The home page doesn't seem to be served from LS cache but W3 Total Cache..

Anything served out of LS cache has "X-LiteSpeed-Cache: hit" in its response header. This one does not have such response header.

W3 Total cache has been disabled a loong time ago, just before I posted about it being slow. All plugins have been disabled since then.

LS Cache was only recently turned off, and the error went. FWIW, I wasn't getting the error in Safari (MAC), but Firefox, (MAC) was, and it could see a cached version of the page.

webizen · #14 06-01-2011, 03:51 PM

turn off FF browser cache to see any difference.

Following is the response header received in Firefox (Mac). Still served from W3 Total Cache.

Quote:

Content-Encoding: gzip
Vary: Accept-Encoding
Date: Wed, 01 Jun 2011 22:46:36 GMT
Server: LiteSpeed
Accept-Ranges: bytes
Connection: close
Etag: "cc8-4de58df9-0"
Last-Modified: Wed, 01 Jun 2011 00:55:21 GMT
Content-Type: text/html; charset=UTF-8
Content-Length: 3272
Pragma: public
Cache-Control: public, must-revalidate, proxy-revalidate, max-age=-75075
X-Powered-By: W3 Total Cache/0.9.2.2
Expires: Wed, 01 Jun 2011 01:55:21 GMT

04nunhucks · #15 06-01-2011, 04:05 PM

Quote:

Originally Posted by webizen

turn off FF browser cache to see any difference.

Following is the response header received in Firefox (Mac). Still served from W3 Total Cache.

It is now deactivated.