TheOptimizationIdiot - 3:15 am on May 3, 2013 (gmt 0)
You're confusing two different things.
Google's search index cache has nothing to do with "proxy serving" and "proxy caching".
AppSpot, even if used as a proxy is very likely not caching your page. (That's even what the denial of your DMCA says.)
It's very likely the user is running a very simple script and "grabbing" the pages from your server on-the-fly, then showing them. (That's abuse of AppSpot's service imo, but not AppSpot itself doing anything against web protocol or "caching" your page like it looks like you said it was in your DMCA complaint and have said a number of times in this thread.)
When I say simple, I mean with mod_rewrite and php I could serve your pages with less than 5 lines of code:
RewriteRule .? /get-the-page.php [L]
### on /get-the-page.php ###
So simple, but it's not "cached" on my server or my host or on AppSpot if that's where I do it from, so AppSpot is working correctly.
To "cache" (save) a copy of your site locally takes about another 5 lines max, but me telling the server to save a copy locally when it "grabs" the page is still not AppSpot "caching" the page as a proxy server, just like the denial of your DMCA notice says.
Google's search cache is another story from another portion of the company, which has nothing to do with AppSpot "caching" of anything, and Google's Search Index keeps a "cached" a copy of every page it grabs when it does not receive an error or find "noarchive" on the page.
Why would they not take the cache out of the search index? Quite possibly because you told them it was AppSpot being used as a proxy server and caching the page.
You didn't ask them to remove the appspot subdomain and cached copy from their search results.
You said AppSpot was misbehaving and caching the page and when they checked they got back to you with exactly what I'm telling you: AppSpot is working just fine and complying with web standards.
I can understand why they "didn't get what you meant" with the DMCA, because the way you have things worded here in this thread made it very difficult to figure out what you're trying to say, which I think is:
Google's search index has a cached copy of a page(s) from your client's site that is being served without their permission on an AppSpot subdomain(s).