After analyzing the server it seems like there are some cache developer
issues which are not known to me.
the main problem with the page is:
The Last-Modified header's value isn't a valid date.
since the headers are:
Expires: Sun, 19 Nov 1978 05:00:00 GMT
Last-Modified: Sun, 19 May 2013 19:47:08 +0000
which a bit unreasonable.
The reasons are: old expiration date and changing last modified headers.
The main problem of the slow site is not the cache or html or DB issues.
the main problem IS CPU over usage since there is an internal CAPTCHA
thingy that works but not like a charm.
ideas on how to solve it??
My answer is to replace this internal CAPTCH plugins inside of drupal to
something with google CAPTCHA which will take a lot of load from this
small server to another server.
Notice that the main issue is picture calculation which is not really
required in this specific server.
The above is one issue.
Another issue is that I want in this specific case to force cache for
the static print pages.
I will be happy to hear the best way to force it.
Thanks,
Eliezer
On 5/6/2013 6:52 PM, Eliezer Croitoru wrote:
I am doing a small non for profit consult for a company in my country
which currently have these headers and they result a lot of tcp_miss on
3.head (two month old).
data can be seen at:
http://redbot.org/?uri=http%3A%2F%2Fagadastories.org.il%2Fnode%2F265
and at:
http://redbot.org/?descend=True&uri=http://agadastories.org.il/node/265
To make this site cache-able there is a need to change couple things
like expiration etc.
I would like to share this scenario to allow others see good settings on
web server and cache proxy.
Thanks,
Eliezer
