2Yervand
Ya zanimalsya etoy problemoy.
I ponyal, chto nereal'no garantirovanno za****it'sya ot skachivaniya.
Khotya mogu perechislit' neskol'ko mne ponravivshikhsya mekhanizmov.
1. Ispol'zovanie mod_rewrite. Eto OCHEN" gibkiy mekhanizm perepisyvaniya URI. Esli na site-e rabotaet kakoy libo vnutrenniy mekhanizm podscheta hit-ov - to mozhno sovmestit' ispol'zovanie external program dlya mod_rewrite i etogo counter-a zapreshaya obrasheniya tomu hostu, kotoriy pereshel nekiy limit (naprimer > 500 zaprosov/min). Minusy - bol'shaya zagruzzka processor-a na servere i bol'shaya nagruzka na DB, v sluchae esli counter ispol'zuet DB. Da i sam mod_rewrite slishkom zzhaden do resursov.
==Apache docs==
RewriteCond %{REMOTE_HOST} ^host1.* [OR]
RewriteCond %{REMOTE_HOST} ^host2.* [OR]
RewriteCond %{REMOTE_HOST} ^host3.*
RewriteRule ...some special stuff for any of these hosts...
==skip==
RewriteCond %{HTTP_USER_AGENT} ^Mozilla.*
RewriteRule ^/$ /homepage.max.html [L] RewriteCond %{HTTP_USER_AGENT} ^Lynx.*
RewriteRule ^/$ /homepage.min.html [L] RewriteRule ^/$ /homepage.std.html [L]
==end of Apache docs===
2. Khranit' postoyanno obnovlyaemiy i teryayushiy actual'nost' content. Konechno etot podkhod priemlem tol'ko dlya ogranichennogo kol-va site-ov (naprimer novostnie), no esli podumat' v etom napravlenii - to mozhno chto-to pridumat'.
3. Sdelat' nemnogo khitruyu navigatsiyu. A imenno dat' vozmozhnost' user-u poluchit' informatsiyu v raznom otyobrazhenii. Tumanno poluchilos' - no vot primer:
http://news.panarmenian.net/rus/headlines/
Kazhdaya novost' dostizhima v 2 variantakh - v novom okne i v tom zhe okne.
Smysl vsego etogo khozyastva pomimo udobstva user-a, eshe i v tom, chto Kakoy-to tam teleport pro poymet i novoe okno, i polezet v to zhe okno. Poluchit v zuby do cherta ssylok i process skachivaniya udlinitsya do bezbozhnosti.
4. Umen'**** ' razmer stranichek uvelichiv ikh kol-vo. Neizvestno naskol'ko eto pomozhet vospriyatiyu informatsii, no esli nayti optimal'noe reshenie - to etot metod v peresechenii s 3 daet fantasticheskie resul'taty. Obychno eti kachalki skachivayut vse files v odnu direktoriyu. A chem bol'she files v working direktorii - tem medlennee rabotaet danniy proces. Eto spravedlivo kak dlya UNIX s ego prekrasnym wget-om, tak i dlya windows. Kak tol'ko kol-vo files zashkalit za 5-6K, process tormozit, i perestaet byt' effektivnym. Pri vsem etom razmer skachannogo site-a na diske stanovitsya uzhasayushe bol'shim. A vremya etogo downloada ochen' dolgim.
JFYI W2000 (PII, 256 RAM) stiral direktoriyu s 37000 files okolo 3 chasov.....
5. zapretit' skachivat' files ne cherez vash referer. Mozhet eto ne sovsem v kassu - no mozhet navesti na mysli. Menya navel.
SetEnvIfNoCase Referer lib\.ru internal_referer
SetEnvIfNoCase User-Agent Teleport internal_referer
SetEnvIfNoCase User-Agent Vampire internal_referer
SetEnvIfNoCase User-Agent ReGet internal_referer
SetEnvIfNoCase User-Agent GetRight internal_referer
SetEnvIfNoCase User-Agent Wget internal_referer
<Files ~ "\.zip$">
ErrorDocument 403
http://lib.ru/books/index.htm
order deny,allow
deny from all
allow from env=internal_referer
</Files>
Vse primery configuratsii dlya apache-1.3.xx
ispol'zovannaya literatura:
http://httpd.apache.org/docs/
http://library.web.am/win/WEBMASTER/sowetywww2.txt
Vot i vse. Esli chto neponyatno - obyasnyu podrobnee.
Regards
AntiGrabbing
