Geolocation Pricing and Caching

Hi,

Please open your .htaccess, after the line

RewriteRule .* - [E=Cache-Control:no-autoflush]

add this code

RewriteRule .* - [E=Cache-Vary:wmc_current_currency]

that block , should look like this:

<IfModule LiteSpeed>
RewriteEngine on
CacheLookup on
RewriteRule .* - [E=Cache-Control:no-autoflush]
RewriteRule .* - [E=Cache-Vary:wmc_current_currency]

Remove the Do-not-cache-cookie , purge all , and see how it goes.

Best regards,

Alright, it looks like it works.

The currency is not been cached by the server anymore.

But its cached by the browser. To figure out by VPN i clear the browser cache (cookies) or change the browser and as well currency changes regarding to the country.

So for first time visitor the right currency will be shown, if i get this right !?

It also works with cookie exclusion (wmc_current_currency)

Thank you ??

Hi,

It also works with cookie exclusion (wmc_current_currency)

This basically tell server not-to-cache when that cookie exist.

My solution is to tell server vary on that cookie

let’s say when cookie = eur , it sends cache1 , when cookie = usd , it sends cache2.

So for first time visitor the right currency will be shown, if i get this right !?

I am not sure , that may depend on how your plugin does it, but if that cookie is set , server will determinate which cache it sends by checking the cookie value.

Best regards,

Ok, i have to test a bit more.

Thanks for the support.

Great Plugin, i got really good results!

Greetings

Hmm, now that i need wpml for other languages the loading time is up to five times higher. I guess not a caching issue.

Well i think geolocation ip based to show currencies is out of the question.

I read something about the Aeila Currency Switcher for WooCommerce in combination with comet cache. They solved it with dynamic caching.

Anyway thanks

If the loading time increased and the other languages’ page isn’t cached, just check the response headers, see if that request is cached or not, if not, log can tell why.

Generally speaking, vary mentioned by @qtwrk should easily fix this issue.