TheOptimizationIdiot - 3:33 pm on May 4, 2013 (gmt 0)
The Appspot caches are dropping, albeit at a slow pace.
You keep calling them AppSpot caches. That would be really confusing to anyone, because they're not AppSpot caches. They're Google's Search Index cache of your clients pages displayed via AppSpot subdomain.
If Appspot subdomains are indexed in Google with my client's homepage, how a user accomplishes this should not matter to the owner of Appspot (Google) when they receive a DMCA notice.
If you don't say what's actually happening no one knows where to actually look to see what you're saying. I understand you're a designer and this isn't your "thing", but that doesn't mean Google should have to somehow determine for you the complaints you're making are about something other than what you keep stating.
I'm really not sure if they can make that determination legally when it comes to DMCA, so your repeatedly calling Google's Search Index cache of your client's page served via AppSpot subdomain an AppSpot cache could very easily be shooting you in the foot.
AppSpot is not caching anything. That's what people keep telling you, but you keep referring to it as an AppSpot cache. AppSpot is not doing any caching. Period. There's a cache of a page served via AppSpot subdomain you would like removed from Google's search cache/index. They're two totally different things.
Whether this is related to the original DMCA notices or htaccess restrictions is uncertain.
Everything to do with the htaccess, nothing to do with a DMCA that talks about AppSpot caches, because AppSpot is not using caching, but that's what you keep saying.