hey all,

boost is caching pages that include the google analytics caching ID. it's creating a mess of cached pages that will never be accessed again. how do i disable this?

here's a screenshot from my server. the page that needs to be cached is north_carolina_html. everything else is superfluous and seems to be causing memory issues.
http://take.ms/GAsAn

any and all help much appreciated.

debra

Comments

Anonymous’s picture

Anonymous (not verified) commented
Category: Bug report » Support request
Status: Active » Closed (works as designed)

Your .htaccess rules will have a series of conditions [OR] statements, adding a rule like

RewriteCond %{QUERY_STRING} !^gclid= [OR]

to the top or centre of the block of conditions will skip boost.

...seems to be causing memory issues.

this is extremely unlikely.

The gclid parameter is a google click id. The solution above will stop the caching but if the logs show that the page is visited once only with a differing gclid then you need a different set of rules to strip out the parameter and redirect to the base page. Boost is not causing any memory problems, the web server is sending out pages that are generated as requested, boost is then storing the generated pages. If the pages are being hit once only then you get more boost stored pages, if not then you save a load of memory/ processing database connections. If the pages are only being served once (with a unique gclid) then the server load is identical apart from the file write at the end of each page, the memory used is identical since boost writes out that which is already in memory.

The issue is more along the lines of that the server is not capable of handling the requests it is receiving and the solution is to use a set of rewrite rules to redirect the gclid pages to the page already cached without the gclid which would reduce the server load by

number of gclid page requests X load to serve one an uncached PHP page