The IP comes back to the Magento site, so it must be some kind of reporting feature for Magento… Telling them how many stores are using Magento or something like that? Dont see why it needs to be sent on every page though.
Well this answers my question that Varien never responded to (http://www.magentocommerce.com/boards/viewthread/18880/)
TYVM. I can now block my server from accessing that IP.
edit: I’ve now blocked my server from accessing their entire subnet. My site is literally twice as fast now, I’m elated. If you’re on a dedicated server, I can tell you how I did it (just PM me)
I also have been following this. However, I am not sure what is really going on so it would be great if Varien would like to comment.
I know already that the store connects to the Magento website in the admin - to check for updates etc. Also - the default footer in the default theme has a link to the Magento website - but I have removed that. Not sure if there was anything else in that code that phoned home.
Now - if it’s only phoning home in the admin - fine. HOWEVER - do give us an option of switching it off.
It it’s phoning home in the frontend - NOT FINE. Let us know what to remove and definitely make it optional and transparent.
Yes - if you block Magento from your server, Magento Connect will likely break. I do my upgrades manually (don’t use MC), so it’s no big deal for me. But if you’re at all unsure, don’t implement what I suggested
Any ideas on what to search for in the code? It might be buried in the library code in something very basic.
But would it be a read or a write? Can you tell?
What’s the trick to blocking the IP? I don’t see any obvious way to do that in my site control panel…
I have searched for all kinds of code but came up with nothing. It would be great to know exactly where from this connection is generated so we can remove that part of the code.
here are most of the places in the code where calls of some kind are being made. Most for connect, but some like for Google Checkout seem a bit strange.
@skippybosco - thanks for the investigative work, much appreciated. So it looks like most of the calls being made are from the admin and for Google Checkout, right? Is there anything there to indicate that there is a call being made to Varien from every page loaded in the frontend?
Sorry I’ve been gone so long Yes, I also think it’s ridiculous that it’s being so invasive. When blocking the IPs in question, the site itself loads much faster. The Admin page however, takes much longer to come up. I believe this is because it’s trying like crazy to ‘phone home’. To me, the benefits outweigh the slow admin page