TheOptimizationIdiot - 1:23 am on May 2, 2013 (gmt 0)
Well, for one the reviewer doesn't even know proper English:
Please note that the webmaster can employing technical measures to block web proxies.
FTEM (Fixed the Email): Please note that the webmaster can employ technical measures to block web proxies.
Beyond that, I have said previously Google's proxy is behaving correctly, so it's really the responsibility of the site owner (now passed to you) to make sure you deny proxies the ability to cache the pages, because if you do not and they run their end of the proxy server according to w3 standards, then your client (now you receiving the "passed buck" from them) don't have anything to complain about.
It's not Google's or anyone else's fault the site owner didn't take the time to learn the web standards and make sure their pages should not be served via proxy before they hopped online. It's really not, and Google may be offensive and abrasive and completely suck at customer service, but a one of the things they're not known to do without great reason is break HTTP protocol.
Sorry for sounding harsh, but it's not right to blame them for following web protocol when you don't know what web protocol is or how to make sure what you want is communicated in a protocol compliant way.
(Complaining because Google follows protocol your client (now you) don't know is like your client complaining they turned right and got hit because they don't understand the Yield Sign for their lane means they have to stop if there's a car coming. It's not the other driver's fault your client doesn't know what they're doing and didn't take the time to learn the systems. It's the fault of the person not knowing WTF the Yield Sign means for not taking the time to learn.)
There are times when Googles seem to be the problem, but it's rarely them not following web protocol standards and on the very limited occasions they break protocol (like treating 302 redirects like 301s) they have very good reason to not follow the exact protocol set by the w3.
If your client does not want their pages cached by Google's proxy server at AppSpot, then they (or now you) need to follow the protocol to stop them from being cached rather than getting upset at Google for following web standards your client has not bothered to learn.
And that still does not stop them from being proxy served, only cached by Google's AppSpot servers.