Forum Moderators: phranque

Message Too Old, No Replies

Blocking hijacking via Google application appspot

         

dolcevita

2:59 pm on Apr 11, 2011 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Is there any way to block hijakcing of proxy server using Google application appspot.

I've seen this discussion in past
[webmasterworld.com...]

but just wonder of there is any other way via htaccess?

Thanks.

wilderness

3:31 pm on Apr 11, 2011 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Unless you provide a raw log entry, which includes the IP range and User Agent, nobody is going to be able to assist you.

If the thread link you provided is correct and these visits/requests are the result of a notorious server farm [webmasterworld.com], that Pfui has been building the linked thread for your benefit.

Another user asked the near-same question [webmasterworld.com] in the SSID forum a few days ago

dolcevita

4:41 pm on Apr 11, 2011 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



It is google IP ranges because appspot is Google application:
NetRange: 72.14.192.0 - 72.14.255.255
CIDR: 72.14.192.0/18


User agent is:
AppEngine-Google; (+http://code.google.com/appengine; appid: proxy-sv)

But i was not able to block it in any way. Blocking IP address should block Google IP ranges and nobody want that.

I was not able from other side to block User Agent via htaccess.

wilderness

5:00 pm on Apr 11, 2011 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



There are numerous IP ranges at google that are NOT in any way related to their crawlier indexing.

You may safely deny this without any detrimental effect on your site being crawled or your pages being indexed.

Unless of course, you require use of Google Apps.

deny from 72.14.192.0/18
SetEnvIf User-Agent appengine keep_out

Note; "keep-out" or whatever relative term you use and have defined.

wilderness

5:06 pm on Apr 11, 2011 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



BTW, just because they are google and/or represent themselves as google, doesn't mean that a webmaster may note exceptions to the "sacred name of google".

here's a some what related thread [webmasterworld.com]

dolcevita

5:45 pm on Apr 11, 2011 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Thank you for help. I'm still a bit scared to block whole IP ranges 72.14.192.0/18

Instead of that i have blocked appengine. Hopefully it will not affect Google Adsense and Google search engine indexeren.

Just question.
Is there any different between
SetEnvIf User-Agent appengine keep_out
and
SetEnvIfNoCase User-Agent "^appengine" keep_out

THanks

wilderness

7:51 pm on Apr 11, 2011 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



# contained anywhere in UA
SetEnvIf User-Agent appengine

# UA MUST Begin with appengine
SetEnvIfNoCase User-Agent "^appengine"

BTW the explanation in Apache of explaining the use of quotes (exactly as), it may cause you some issues, perhaps not even function as you intended.

I've used quotes sparringly for more than ten years, and only when I desired an "exactly as" application of the expression.

jdMorgan

9:39 pm on Apr 14, 2011 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Note that the quotes are required to enclose regular-expressions patterns which contain spaces for SetEnvIf and RedirectMatch, and other "xxMatch" directives. In mod_rewrite, they're not necessary for this purpose because you can use backslash-escapes instead if desired.

Jim