Forum Moderators: phranque

Message Too Old, No Replies

Blocking Amazonaws with .htaccess

         

JohnG

10:19 pm on Sep 14, 2014 (gmt 0)

10+ Year Member



The following topic should either be updated to reflect correct procedures for blocking amazonaws, or deleted since the procedure described does not work.

[webmasterworld.com...]

phranque

9:10 am on Sep 15, 2014 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



blocking scrapers is a moving target.

what procedures are currently working for you?

in any case, our most current discussions on this subject would be in the Search Engine Spider and User Agent Identification: forum:
http://www.webmasterworld.com/search_engine_spiders/ [webmasterworld.com]

for example - Amazon AWS Hosts Bad Bots:
http://www.webmasterworld.com/search_engine_spiders/4574827.htm [webmasterworld.com]

incrediBILL

8:02 pm on Sep 15, 2014 (gmt 0)

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



The method used in the post referenced does require reverse DNS enabled in Apache which many hosts don't enable by default.

FWIW, we don't update old posts because the content was valid at the time it was posted. If we did update old posts all we would do it run around all day updating old legacy posts, there's a ton of them, many out of date. This isn't unique to WebmasterWorld, many forums have out of date legacy posts.

phranque

9:17 pm on Sep 15, 2014 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



we don't update old posts because the content was valid at the time it was posted... many forums have out of date legacy posts


IMO, historical methods are still good information - it's good to know what's been tried, whether or not it still works.