Website Prospector - CDNs - Cloudflare - how to resolve?
Hi all - Question for users out there.
We just switched our hosting model to use a CDN (Content Delivery Network) called Cloudflare, in hopes of boosting local traffic in the US. (Main site is currently hosted in Australia). So visitors are accessing the site I believe through this CDN.
An unintended consequence seems to be on the Website Prospector reports. Nearly all of the visitors (anonymous AND known) are suddenly showing up with the company = Cloudflare.
It's one thing when you get random IP addresses like AT&T or Cox. It's another to have *everyone* show up as Cloudflare.
Does anyone know if there's anything we can do, any setting to change, to go back to making the original source visible? I know AO contracts to a third-party to get the IP data so I'm thinking we have to go back through the CDN somehow but thought I'd see if anyone has any ideas?
Thanks,
Karen
------------------------------
Karen Oakland
Intelledox
karen.oakland@intelledox.com
------------------------------
We just switched our hosting model to use a CDN (Content Delivery Network) called Cloudflare, in hopes of boosting local traffic in the US. (Main site is currently hosted in Australia). So visitors are accessing the site I believe through this CDN.
An unintended consequence seems to be on the Website Prospector reports. Nearly all of the visitors (anonymous AND known) are suddenly showing up with the company = Cloudflare.
It's one thing when you get random IP addresses like AT&T or Cox. It's another to have *everyone* show up as Cloudflare.
Does anyone know if there's anything we can do, any setting to change, to go back to making the original source visible? I know AO contracts to a third-party to get the IP data so I'm thinking we have to go back through the CDN somehow but thought I'd see if anyone has any ideas?
Thanks,
Karen
------------------------------
Karen Oakland
Intelledox
karen.oakland@intelledox.com
------------------------------
Please sign in to leave a comment.
Comments
0 comments