After doing some SEO and Google AdWords,
my site began to serve tons of requests with ?gclid=[GOOGLE_AD_TRACKINGCODE] query string parameter.
When looking to the response header,
X-Hyper-Cache:stop – query string
I found that Hyper Cache didn’t hit the cache for this case.
So we encountered high CPU load for these requests.
In fact, we didn’t serve any different results for this gclid parameter.
So I should recommend that Hyper Cache to have some option to serve the (query string neutral) cached content for matched sets of configured parameters.
And also option to cache and serve query string varied for some matched sets of configured parameters.
-
This topic was modified 19 hours, 5 minutes ago by
ittipan. Reason: Clarify
