Hi Stanley,
Every time I get a message from you i am put up against another wall… simply put, what you’re telling me is not concise and i simply don’t understand it as im getting conflicting information from other sources.
If you give me a proper set of instructions on the process from start to finish, I should be able to easily do this myself, however, i have yet to get those.
I have contacted our hosting support who have advised me that:
Thanks for your ticket.
The GEOIP module for Apache is already installed.
There is no cookie that is generated. What is sounds like you might be after, is the PHP variables that can be used when that module is enabled.
There is some documentation on that here https://www.php.net/manual/en/geoip.constants.php
Can you please explain the process/what is happening here as my understanding is not complete as you have not really advised on whats going on here and what we are trying to achieve.
From my understanding, this is what is happening:
1) Booster (or woo) produce a GEOIP cookie.
2) We need to get htaccess to VARY the cookie produced by Booster/Woo using the Apache GEOIP module we have installed.
Is this right? I still dont see how is this going to fix cached page HTML etc? Is there other steps here? Can you give me an exact use case scenario/set of steps of how i set this up this solution.?