Php cracking apache, nginx, and iis anti-Leech images

Currently, most websites have anti-Leech protection. apache, nginx, and iis are the most commonly used anti-Leech protection settings. Are these settings not broken? is the answer correct, let's take a look at the method of cracking. A host of its own is generally designed as quot ;... currently, most websites have anti-Leech protection. apache, nginx, and iis are the most commonly used anti-Leech protection settings. Are these settings not broken? is the answer correct, let's take a look at the method of cracking.

You can design anti-Leech protection for your host, including image anti-Leech protection and download anti-Leech protection, for example:

Use. htaccess to set anti-Leech

RewriteEngine onRewriteCond %{HTTP_REFERER} !^$RewriteCond %{HTTP_REFERER} !^http://(www.)?xuexb.com/.*$ [NC]RewriteRule .(gif|jpg)$ http://www.phprm.com /image.gif [R,L]

Set anti-Leech for nginx

location ~* .(gif|jpg|png|swf|flv)$ {    valid_referers none blocked phprm.com;    if ($invalid_referer) {        rewrite ^/ http://phprm.com /234_s.gif;        #return 404;    }}

But how to crack anti-leech? Generally, anti-Leech is used to determine whether the origin is your own domain name. we can use the file_get_contents method built in php to request this image (of course, other backend languages also have similar methods), such:

// GetImg. php? Url = target Image connection

Php code snippets:

1. directly load anti-Leech images:

Anti-leech attack

2. read images through php:

Anti-leech attack

Address:

Reprinted at will, but please attach the article address :-)