Bizarre Slowdown для некоторых пользователей с директивой .htaccess

Чтобы защитить свой website от общего плана хостинга, я добавил его в мой file .htaccess:

<Limit GET HEAD POST> order deny,allow deny from .ru deny from .cn deny from .in deny from .de deny from .cz deny from .kp deny from .kr deny from .ng deny from .pk # other allows go here -- below is just a sample allow from 10.10.10. </Limit> 

Я бежал вот так целый год без проблем. Я также знаю, что это сработало, потому что какой-то парень из Германии сказал: «Эй, я слышал о вашем websiteе, но я не могу подkeyиться к нему». Поэтому я должен был доверять ему и проткнуть ему дыру. Затем он сказал: «Я вижу ваш website. Спасибо!» (Причина, по которой я блокирую вышеуказанные страны, в два раза – одна, они не мои целевые клиенты вообще, и два, я получал тяжелый трафик spambot из этих стран.)

Однако в течение недели назад server общего плана хостинга был обновлен до последних CentOS и cPanel. Теперь я вдруг получаю от 13 до 15 секунд. Если я прокомментирую вышеприведенный блок, то никаких замедлений вообще – супербыстрая загрузка страниц.

Я тестировал на своих рабочих станциях Linux и Windows дома testing с помощью Opera, Safari, Chrome, Firefox и IE. Мой сосед, работающий под Windows и Firefox, находится на Frontier Communications DSL, как и я, и у нее такая же латентность.

Мои клиенты и веб-хостинг-провайдер также получают мгновенные загрузки страниц. Это связано только с DSL Frontier Communications.

Я заменил свой DNS как тест. В Linux я могу отредактировать свой file /etc/resolv.conf и использовать Google DNS, и Интерless становится быстрее. Однако, опять же – все еще латентность для моего websiteа.

Я знаю, что если я вызову Frontier, все, что они скажут, это они не знают, почему возникает проблема, и что проблема заkeyается в веб-хостинг-провайдере. Когда я позвонил своему веб-хостинг-провайдеру (a2hosting.com), они сказали мне, что проблема связана только с моим провайдером, Frontier Communications и что я должен их назвать.

В чем причина этой медлительности только с Frontier Communications?

Ограничение по домену означает, что для каждого requestа apache необходимо выполнить обратный search DNS. Здесь происходит замедление. Для этого less простого обходного пути.

Обновление. Обходным путем было бы реализовать геоинформацию в вашем приложении, чтобы решить, откуда приходит request (см. Здесь ). С этим ваш website будет невероятно быстрым по сравнению с тем, что у вас есть сейчас.

вы можете заблокировать ips напрямую: http://www.wizcrafts.net/chinese-blocklist.html

Это был ответ, который я адаптировал от @Oliver.

Он был прав – внезапно у этого провайдера веб-хостинга возникли серьезные проблемы с обратными DNS-searchами, а Verizon (и, следовательно, Frontier Communications, которая выкупила большинство сельских счетов Verizon DSL), славится тем, что медленна в предоставлении всех необходимых ответов на обратный DNS звонки. Я имею в viewу, я заметил, что некоторые SSH-соединения, которые я делаю с различными serverами в Интерlessе, медленны, потому что мой интерless-провайдер неправильно работает с обратным DNS.

Поэтому мне понадобилось обходное решение. Я реализовал его так:

 # I HAVE NO FREAKING IDEA WHAT THIS DOES, BUT CPANEL AUTOMATICALLY CREATES IT <Files 403.shtml> order allow,deny allow from all </Files> # THIS IS FOR FUTURE EXPANSION -- I CAN DENY BY INDIVIDUAL IP ADDRESSES HERE, # OR I CAN ALLOW CERTAIN IP ADDRESS HERE. I CANNOT, HOWEVER, ADD DOMAIN TLDS LIKE # .ru HERE BECAUSE OF THE REVERSE DNS SLOWDOWN WITH THIS WEB HOSTING PROVIDER. # FOR THAT, I USE THE REWRITE RULES BELOW. <Limit GET HEAD POST> order deny,allow </Limit> # THIS IS IMPORTANT. WHAT IT DOES IS LOOK AT ALL THE OTHER HTTP TYPE OF ACTIVITIES # LIKE WEBDAV (A SECURITY HOLE, POTENTIALLY) AND BLOCK THOSE, LEAVING ONLY NORMAL # BROWSER STUFF WHICH IS ALWAYS POST, HEAD, AND GET. <LimitExcept POST HEAD GET> deny from all </LimitExcept> # TURN ON REWRITE RULES RewriteEngine on # CHECK THE HOST NAME SENT BY THE BROWSER AND BLOCK IT WITH 403 FORBIDDEN IF # FROM PARTICULAR COUNTRIES. RewriteCond %{REMOTE_HOST} \.ru [NC,OR] RewriteCond %{REMOTE_HOST} \.cn [NC,OR] RewriteCond %{REMOTE_HOST} \.in [NC,OR] RewriteCond %{REMOTE_HOST} \.de [NC,OR] RewriteCond %{REMOTE_HOST} \.cz [NC,OR] RewriteCond %{REMOTE_HOST} \.kp [NC,OR] RewriteCond %{REMOTE_HOST} \.kr [NC,OR] RewriteCond %{REMOTE_HOST} \.ng [NC,OR] RewriteCond %{REMOTE_HOST} \.pk [NC] RewriteRule .* - [F] # NOW PLACE YOUR OTHER REWRITE RULES YOU MAY HAVE HERE. # У меня НЕ СМОТРЕТЬ ИДЕЮ, ЧТО ЭТО ДЕЛАЕТ, НО СКАНЕЛЬ АВТОМАТИЧЕСКИ СОЗДАЕТ ЭТО # I HAVE NO FREAKING IDEA WHAT THIS DOES, BUT CPANEL AUTOMATICALLY CREATES IT <Files 403.shtml> order allow,deny allow from all </Files> # THIS IS FOR FUTURE EXPANSION -- I CAN DENY BY INDIVIDUAL IP ADDRESSES HERE, # OR I CAN ALLOW CERTAIN IP ADDRESS HERE. I CANNOT, HOWEVER, ADD DOMAIN TLDS LIKE # .ru HERE BECAUSE OF THE REVERSE DNS SLOWDOWN WITH THIS WEB HOSTING PROVIDER. # FOR THAT, I USE THE REWRITE RULES BELOW. <Limit GET HEAD POST> order deny,allow </Limit> # THIS IS IMPORTANT. WHAT IT DOES IS LOOK AT ALL THE OTHER HTTP TYPE OF ACTIVITIES # LIKE WEBDAV (A SECURITY HOLE, POTENTIALLY) AND BLOCK THOSE, LEAVING ONLY NORMAL # BROWSER STUFF WHICH IS ALWAYS POST, HEAD, AND GET. <LimitExcept POST HEAD GET> deny from all </LimitExcept> # TURN ON REWRITE RULES RewriteEngine on # CHECK THE HOST NAME SENT BY THE BROWSER AND BLOCK IT WITH 403 FORBIDDEN IF # FROM PARTICULAR COUNTRIES. RewriteCond %{REMOTE_HOST} \.ru [NC,OR] RewriteCond %{REMOTE_HOST} \.cn [NC,OR] RewriteCond %{REMOTE_HOST} \.in [NC,OR] RewriteCond %{REMOTE_HOST} \.de [NC,OR] RewriteCond %{REMOTE_HOST} \.cz [NC,OR] RewriteCond %{REMOTE_HOST} \.kp [NC,OR] RewriteCond %{REMOTE_HOST} \.kr [NC,OR] RewriteCond %{REMOTE_HOST} \.ng [NC,OR] RewriteCond %{REMOTE_HOST} \.pk [NC] RewriteRule .* - [F] # NOW PLACE YOUR OTHER REWRITE RULES YOU MAY HAVE HERE. <Файлы 403.shtml> # I HAVE NO FREAKING IDEA WHAT THIS DOES, BUT CPANEL AUTOMATICALLY CREATES IT <Files 403.shtml> order allow,deny allow from all </Files> # THIS IS FOR FUTURE EXPANSION -- I CAN DENY BY INDIVIDUAL IP ADDRESSES HERE, # OR I CAN ALLOW CERTAIN IP ADDRESS HERE. I CANNOT, HOWEVER, ADD DOMAIN TLDS LIKE # .ru HERE BECAUSE OF THE REVERSE DNS SLOWDOWN WITH THIS WEB HOSTING PROVIDER. # FOR THAT, I USE THE REWRITE RULES BELOW. <Limit GET HEAD POST> order deny,allow </Limit> # THIS IS IMPORTANT. WHAT IT DOES IS LOOK AT ALL THE OTHER HTTP TYPE OF ACTIVITIES # LIKE WEBDAV (A SECURITY HOLE, POTENTIALLY) AND BLOCK THOSE, LEAVING ONLY NORMAL # BROWSER STUFF WHICH IS ALWAYS POST, HEAD, AND GET. <LimitExcept POST HEAD GET> deny from all </LimitExcept> # TURN ON REWRITE RULES RewriteEngine on # CHECK THE HOST NAME SENT BY THE BROWSER AND BLOCK IT WITH 403 FORBIDDEN IF # FROM PARTICULAR COUNTRIES. RewriteCond %{REMOTE_HOST} \.ru [NC,OR] RewriteCond %{REMOTE_HOST} \.cn [NC,OR] RewriteCond %{REMOTE_HOST} \.in [NC,OR] RewriteCond %{REMOTE_HOST} \.de [NC,OR] RewriteCond %{REMOTE_HOST} \.cz [NC,OR] RewriteCond %{REMOTE_HOST} \.kp [NC,OR] RewriteCond %{REMOTE_HOST} \.kr [NC,OR] RewriteCond %{REMOTE_HOST} \.ng [NC,OR] RewriteCond %{REMOTE_HOST} \.pk [NC] RewriteRule .* - [F] # NOW PLACE YOUR OTHER REWRITE RULES YOU MAY HAVE HERE. # ЭТО ДЛЯ БУДУЩЕГО РАСШИРЕНИЯ - Я МОГУ ПОЛУЧИТЬ ИНДИВИДУАЛЬНЫМ АДРЕСАМ IP ЗДЕСЬ, # I HAVE NO FREAKING IDEA WHAT THIS DOES, BUT CPANEL AUTOMATICALLY CREATES IT <Files 403.shtml> order allow,deny allow from all </Files> # THIS IS FOR FUTURE EXPANSION -- I CAN DENY BY INDIVIDUAL IP ADDRESSES HERE, # OR I CAN ALLOW CERTAIN IP ADDRESS HERE. I CANNOT, HOWEVER, ADD DOMAIN TLDS LIKE # .ru HERE BECAUSE OF THE REVERSE DNS SLOWDOWN WITH THIS WEB HOSTING PROVIDER. # FOR THAT, I USE THE REWRITE RULES BELOW. <Limit GET HEAD POST> order deny,allow </Limit> # THIS IS IMPORTANT. WHAT IT DOES IS LOOK AT ALL THE OTHER HTTP TYPE OF ACTIVITIES # LIKE WEBDAV (A SECURITY HOLE, POTENTIALLY) AND BLOCK THOSE, LEAVING ONLY NORMAL # BROWSER STUFF WHICH IS ALWAYS POST, HEAD, AND GET. <LimitExcept POST HEAD GET> deny from all </LimitExcept> # TURN ON REWRITE RULES RewriteEngine on # CHECK THE HOST NAME SENT BY THE BROWSER AND BLOCK IT WITH 403 FORBIDDEN IF # FROM PARTICULAR COUNTRIES. RewriteCond %{REMOTE_HOST} \.ru [NC,OR] RewriteCond %{REMOTE_HOST} \.cn [NC,OR] RewriteCond %{REMOTE_HOST} \.in [NC,OR] RewriteCond %{REMOTE_HOST} \.de [NC,OR] RewriteCond %{REMOTE_HOST} \.cz [NC,OR] RewriteCond %{REMOTE_HOST} \.kp [NC,OR] RewriteCond %{REMOTE_HOST} \.kr [NC,OR] RewriteCond %{REMOTE_HOST} \.ng [NC,OR] RewriteCond %{REMOTE_HOST} \.pk [NC] RewriteRule .* - [F] # NOW PLACE YOUR OTHER REWRITE RULES YOU MAY HAVE HERE. # ИЛИ Я МОГУ ПОЗВОЛЯТЬ ОТДЕЛЬНЫЙ IP-АДРЕС ЗДЕСЬ. # I HAVE NO FREAKING IDEA WHAT THIS DOES, BUT CPANEL AUTOMATICALLY CREATES IT <Files 403.shtml> order allow,deny allow from all </Files> # THIS IS FOR FUTURE EXPANSION -- I CAN DENY BY INDIVIDUAL IP ADDRESSES HERE, # OR I CAN ALLOW CERTAIN IP ADDRESS HERE. I CANNOT, HOWEVER, ADD DOMAIN TLDS LIKE # .ru HERE BECAUSE OF THE REVERSE DNS SLOWDOWN WITH THIS WEB HOSTING PROVIDER. # FOR THAT, I USE THE REWRITE RULES BELOW. <Limit GET HEAD POST> order deny,allow </Limit> # THIS IS IMPORTANT. WHAT IT DOES IS LOOK AT ALL THE OTHER HTTP TYPE OF ACTIVITIES # LIKE WEBDAV (A SECURITY HOLE, POTENTIALLY) AND BLOCK THOSE, LEAVING ONLY NORMAL # BROWSER STUFF WHICH IS ALWAYS POST, HEAD, AND GET. <LimitExcept POST HEAD GET> deny from all </LimitExcept> # TURN ON REWRITE RULES RewriteEngine on # CHECK THE HOST NAME SENT BY THE BROWSER AND BLOCK IT WITH 403 FORBIDDEN IF # FROM PARTICULAR COUNTRIES. RewriteCond %{REMOTE_HOST} \.ru [NC,OR] RewriteCond %{REMOTE_HOST} \.cn [NC,OR] RewriteCond %{REMOTE_HOST} \.in [NC,OR] RewriteCond %{REMOTE_HOST} \.de [NC,OR] RewriteCond %{REMOTE_HOST} \.cz [NC,OR] RewriteCond %{REMOTE_HOST} \.kp [NC,OR] RewriteCond %{REMOTE_HOST} \.kr [NC,OR] RewriteCond %{REMOTE_HOST} \.ng [NC,OR] RewriteCond %{REMOTE_HOST} \.pk [NC] RewriteRule .* - [F] # NOW PLACE YOUR OTHER REWRITE RULES YOU MAY HAVE HERE. Я НЕ МОЖЕТ, НИКОГДА, ДОБАВЛЯТЬ ДОМЕНЫ # I HAVE NO FREAKING IDEA WHAT THIS DOES, BUT CPANEL AUTOMATICALLY CREATES IT <Files 403.shtml> order allow,deny allow from all </Files> # THIS IS FOR FUTURE EXPANSION -- I CAN DENY BY INDIVIDUAL IP ADDRESSES HERE, # OR I CAN ALLOW CERTAIN IP ADDRESS HERE. I CANNOT, HOWEVER, ADD DOMAIN TLDS LIKE # .ru HERE BECAUSE OF THE REVERSE DNS SLOWDOWN WITH THIS WEB HOSTING PROVIDER. # FOR THAT, I USE THE REWRITE RULES BELOW. <Limit GET HEAD POST> order deny,allow </Limit> # THIS IS IMPORTANT. WHAT IT DOES IS LOOK AT ALL THE OTHER HTTP TYPE OF ACTIVITIES # LIKE WEBDAV (A SECURITY HOLE, POTENTIALLY) AND BLOCK THOSE, LEAVING ONLY NORMAL # BROWSER STUFF WHICH IS ALWAYS POST, HEAD, AND GET. <LimitExcept POST HEAD GET> deny from all </LimitExcept> # TURN ON REWRITE RULES RewriteEngine on # CHECK THE HOST NAME SENT BY THE BROWSER AND BLOCK IT WITH 403 FORBIDDEN IF # FROM PARTICULAR COUNTRIES. RewriteCond %{REMOTE_HOST} \.ru [NC,OR] RewriteCond %{REMOTE_HOST} \.cn [NC,OR] RewriteCond %{REMOTE_HOST} \.in [NC,OR] RewriteCond %{REMOTE_HOST} \.de [NC,OR] RewriteCond %{REMOTE_HOST} \.cz [NC,OR] RewriteCond %{REMOTE_HOST} \.kp [NC,OR] RewriteCond %{REMOTE_HOST} \.kr [NC,OR] RewriteCond %{REMOTE_HOST} \.ng [NC,OR] RewriteCond %{REMOTE_HOST} \.pk [NC] RewriteRule .* - [F] # NOW PLACE YOUR OTHER REWRITE RULES YOU MAY HAVE HERE. # .ru ЗДЕСЬ ИЗ-ЗА ПЕРЕСМОТРЕННОГО DNS-ВРЕМЕНИ С ЭТОМ ВЕБ-ХОСТИНГ-ПРОВАЙДЕРОМ. # I HAVE NO FREAKING IDEA WHAT THIS DOES, BUT CPANEL AUTOMATICALLY CREATES IT <Files 403.shtml> order allow,deny allow from all </Files> # THIS IS FOR FUTURE EXPANSION -- I CAN DENY BY INDIVIDUAL IP ADDRESSES HERE, # OR I CAN ALLOW CERTAIN IP ADDRESS HERE. I CANNOT, HOWEVER, ADD DOMAIN TLDS LIKE # .ru HERE BECAUSE OF THE REVERSE DNS SLOWDOWN WITH THIS WEB HOSTING PROVIDER. # FOR THAT, I USE THE REWRITE RULES BELOW. <Limit GET HEAD POST> order deny,allow </Limit> # THIS IS IMPORTANT. WHAT IT DOES IS LOOK AT ALL THE OTHER HTTP TYPE OF ACTIVITIES # LIKE WEBDAV (A SECURITY HOLE, POTENTIALLY) AND BLOCK THOSE, LEAVING ONLY NORMAL # BROWSER STUFF WHICH IS ALWAYS POST, HEAD, AND GET. <LimitExcept POST HEAD GET> deny from all </LimitExcept> # TURN ON REWRITE RULES RewriteEngine on # CHECK THE HOST NAME SENT BY THE BROWSER AND BLOCK IT WITH 403 FORBIDDEN IF # FROM PARTICULAR COUNTRIES. RewriteCond %{REMOTE_HOST} \.ru [NC,OR] RewriteCond %{REMOTE_HOST} \.cn [NC,OR] RewriteCond %{REMOTE_HOST} \.in [NC,OR] RewriteCond %{REMOTE_HOST} \.de [NC,OR] RewriteCond %{REMOTE_HOST} \.cz [NC,OR] RewriteCond %{REMOTE_HOST} \.kp [NC,OR] RewriteCond %{REMOTE_HOST} \.kr [NC,OR] RewriteCond %{REMOTE_HOST} \.ng [NC,OR] RewriteCond %{REMOTE_HOST} \.pk [NC] RewriteRule .* - [F] # NOW PLACE YOUR OTHER REWRITE RULES YOU MAY HAVE HERE. # ДЛЯ ТОГО, Я ИСПОЛЬЗУЮТ ПРАВИЛА РЕАЛИЗАЦИИ НИЖЕ. # I HAVE NO FREAKING IDEA WHAT THIS DOES, BUT CPANEL AUTOMATICALLY CREATES IT <Files 403.shtml> order allow,deny allow from all </Files> # THIS IS FOR FUTURE EXPANSION -- I CAN DENY BY INDIVIDUAL IP ADDRESSES HERE, # OR I CAN ALLOW CERTAIN IP ADDRESS HERE. I CANNOT, HOWEVER, ADD DOMAIN TLDS LIKE # .ru HERE BECAUSE OF THE REVERSE DNS SLOWDOWN WITH THIS WEB HOSTING PROVIDER. # FOR THAT, I USE THE REWRITE RULES BELOW. <Limit GET HEAD POST> order deny,allow </Limit> # THIS IS IMPORTANT. WHAT IT DOES IS LOOK AT ALL THE OTHER HTTP TYPE OF ACTIVITIES # LIKE WEBDAV (A SECURITY HOLE, POTENTIALLY) AND BLOCK THOSE, LEAVING ONLY NORMAL # BROWSER STUFF WHICH IS ALWAYS POST, HEAD, AND GET. <LimitExcept POST HEAD GET> deny from all </LimitExcept> # TURN ON REWRITE RULES RewriteEngine on # CHECK THE HOST NAME SENT BY THE BROWSER AND BLOCK IT WITH 403 FORBIDDEN IF # FROM PARTICULAR COUNTRIES. RewriteCond %{REMOTE_HOST} \.ru [NC,OR] RewriteCond %{REMOTE_HOST} \.cn [NC,OR] RewriteCond %{REMOTE_HOST} \.in [NC,OR] RewriteCond %{REMOTE_HOST} \.de [NC,OR] RewriteCond %{REMOTE_HOST} \.cz [NC,OR] RewriteCond %{REMOTE_HOST} \.kp [NC,OR] RewriteCond %{REMOTE_HOST} \.kr [NC,OR] RewriteCond %{REMOTE_HOST} \.ng [NC,OR] RewriteCond %{REMOTE_HOST} \.pk [NC] RewriteRule .* - [F] # NOW PLACE YOUR OTHER REWRITE RULES YOU MAY HAVE HERE. ЧТО ЭТО СМОТРЕТЬ ВСЕ ДРУГОЙ HTTP ТИП ДЕЯТЕЛЬНОСТИ # I HAVE NO FREAKING IDEA WHAT THIS DOES, BUT CPANEL AUTOMATICALLY CREATES IT <Files 403.shtml> order allow,deny allow from all </Files> # THIS IS FOR FUTURE EXPANSION -- I CAN DENY BY INDIVIDUAL IP ADDRESSES HERE, # OR I CAN ALLOW CERTAIN IP ADDRESS HERE. I CANNOT, HOWEVER, ADD DOMAIN TLDS LIKE # .ru HERE BECAUSE OF THE REVERSE DNS SLOWDOWN WITH THIS WEB HOSTING PROVIDER. # FOR THAT, I USE THE REWRITE RULES BELOW. <Limit GET HEAD POST> order deny,allow </Limit> # THIS IS IMPORTANT. WHAT IT DOES IS LOOK AT ALL THE OTHER HTTP TYPE OF ACTIVITIES # LIKE WEBDAV (A SECURITY HOLE, POTENTIALLY) AND BLOCK THOSE, LEAVING ONLY NORMAL # BROWSER STUFF WHICH IS ALWAYS POST, HEAD, AND GET. <LimitExcept POST HEAD GET> deny from all </LimitExcept> # TURN ON REWRITE RULES RewriteEngine on # CHECK THE HOST NAME SENT BY THE BROWSER AND BLOCK IT WITH 403 FORBIDDEN IF # FROM PARTICULAR COUNTRIES. RewriteCond %{REMOTE_HOST} \.ru [NC,OR] RewriteCond %{REMOTE_HOST} \.cn [NC,OR] RewriteCond %{REMOTE_HOST} \.in [NC,OR] RewriteCond %{REMOTE_HOST} \.de [NC,OR] RewriteCond %{REMOTE_HOST} \.cz [NC,OR] RewriteCond %{REMOTE_HOST} \.kp [NC,OR] RewriteCond %{REMOTE_HOST} \.kr [NC,OR] RewriteCond %{REMOTE_HOST} \.ng [NC,OR] RewriteCond %{REMOTE_HOST} \.pk [NC] RewriteRule .* - [F] # NOW PLACE YOUR OTHER REWRITE RULES YOU MAY HAVE HERE. # КАК ВЕБДАВ (ОТВЕРСТИЕ БЕЗОПАСНОСТИ, ПОТЕНЦИАЛЬНО) И БЛОКИРОВКИ, ВЫХОДЯЩИЕ ТОЛЬКО НОРМАЛЬНЫМ # I HAVE NO FREAKING IDEA WHAT THIS DOES, BUT CPANEL AUTOMATICALLY CREATES IT <Files 403.shtml> order allow,deny allow from all </Files> # THIS IS FOR FUTURE EXPANSION -- I CAN DENY BY INDIVIDUAL IP ADDRESSES HERE, # OR I CAN ALLOW CERTAIN IP ADDRESS HERE. I CANNOT, HOWEVER, ADD DOMAIN TLDS LIKE # .ru HERE BECAUSE OF THE REVERSE DNS SLOWDOWN WITH THIS WEB HOSTING PROVIDER. # FOR THAT, I USE THE REWRITE RULES BELOW. <Limit GET HEAD POST> order deny,allow </Limit> # THIS IS IMPORTANT. WHAT IT DOES IS LOOK AT ALL THE OTHER HTTP TYPE OF ACTIVITIES # LIKE WEBDAV (A SECURITY HOLE, POTENTIALLY) AND BLOCK THOSE, LEAVING ONLY NORMAL # BROWSER STUFF WHICH IS ALWAYS POST, HEAD, AND GET. <LimitExcept POST HEAD GET> deny from all </LimitExcept> # TURN ON REWRITE RULES RewriteEngine on # CHECK THE HOST NAME SENT BY THE BROWSER AND BLOCK IT WITH 403 FORBIDDEN IF # FROM PARTICULAR COUNTRIES. RewriteCond %{REMOTE_HOST} \.ru [NC,OR] RewriteCond %{REMOTE_HOST} \.cn [NC,OR] RewriteCond %{REMOTE_HOST} \.in [NC,OR] RewriteCond %{REMOTE_HOST} \.de [NC,OR] RewriteCond %{REMOTE_HOST} \.cz [NC,OR] RewriteCond %{REMOTE_HOST} \.kp [NC,OR] RewriteCond %{REMOTE_HOST} \.kr [NC,OR] RewriteCond %{REMOTE_HOST} \.ng [NC,OR] RewriteCond %{REMOTE_HOST} \.pk [NC] RewriteRule .* - [F] # NOW PLACE YOUR OTHER REWRITE RULES YOU MAY HAVE HERE. # СТРАНИЦА БРАУЗЕРА, КОТОРЫЙ ВСЕГДА ПОЧТА, ГОЛОВА И ПОЛУЧИТЬ. # I HAVE NO FREAKING IDEA WHAT THIS DOES, BUT CPANEL AUTOMATICALLY CREATES IT <Files 403.shtml> order allow,deny allow from all </Files> # THIS IS FOR FUTURE EXPANSION -- I CAN DENY BY INDIVIDUAL IP ADDRESSES HERE, # OR I CAN ALLOW CERTAIN IP ADDRESS HERE. I CANNOT, HOWEVER, ADD DOMAIN TLDS LIKE # .ru HERE BECAUSE OF THE REVERSE DNS SLOWDOWN WITH THIS WEB HOSTING PROVIDER. # FOR THAT, I USE THE REWRITE RULES BELOW. <Limit GET HEAD POST> order deny,allow </Limit> # THIS IS IMPORTANT. WHAT IT DOES IS LOOK AT ALL THE OTHER HTTP TYPE OF ACTIVITIES # LIKE WEBDAV (A SECURITY HOLE, POTENTIALLY) AND BLOCK THOSE, LEAVING ONLY NORMAL # BROWSER STUFF WHICH IS ALWAYS POST, HEAD, AND GET. <LimitExcept POST HEAD GET> deny from all </LimitExcept> # TURN ON REWRITE RULES RewriteEngine on # CHECK THE HOST NAME SENT BY THE BROWSER AND BLOCK IT WITH 403 FORBIDDEN IF # FROM PARTICULAR COUNTRIES. RewriteCond %{REMOTE_HOST} \.ru [NC,OR] RewriteCond %{REMOTE_HOST} \.cn [NC,OR] RewriteCond %{REMOTE_HOST} \.in [NC,OR] RewriteCond %{REMOTE_HOST} \.de [NC,OR] RewriteCond %{REMOTE_HOST} \.cz [NC,OR] RewriteCond %{REMOTE_HOST} \.kp [NC,OR] RewriteCond %{REMOTE_HOST} \.kr [NC,OR] RewriteCond %{REMOTE_HOST} \.ng [NC,OR] RewriteCond %{REMOTE_HOST} \.pk [NC] RewriteRule .* - [F] # NOW PLACE YOUR OTHER REWRITE RULES YOU MAY HAVE HERE. <LimitExcept POST HEAD GET> # I HAVE NO FREAKING IDEA WHAT THIS DOES, BUT CPANEL AUTOMATICALLY CREATES IT <Files 403.shtml> order allow,deny allow from all </Files> # THIS IS FOR FUTURE EXPANSION -- I CAN DENY BY INDIVIDUAL IP ADDRESSES HERE, # OR I CAN ALLOW CERTAIN IP ADDRESS HERE. I CANNOT, HOWEVER, ADD DOMAIN TLDS LIKE # .ru HERE BECAUSE OF THE REVERSE DNS SLOWDOWN WITH THIS WEB HOSTING PROVIDER. # FOR THAT, I USE THE REWRITE RULES BELOW. <Limit GET HEAD POST> order deny,allow </Limit> # THIS IS IMPORTANT. WHAT IT DOES IS LOOK AT ALL THE OTHER HTTP TYPE OF ACTIVITIES # LIKE WEBDAV (A SECURITY HOLE, POTENTIALLY) AND BLOCK THOSE, LEAVING ONLY NORMAL # BROWSER STUFF WHICH IS ALWAYS POST, HEAD, AND GET. <LimitExcept POST HEAD GET> deny from all </LimitExcept> # TURN ON REWRITE RULES RewriteEngine on # CHECK THE HOST NAME SENT BY THE BROWSER AND BLOCK IT WITH 403 FORBIDDEN IF # FROM PARTICULAR COUNTRIES. RewriteCond %{REMOTE_HOST} \.ru [NC,OR] RewriteCond %{REMOTE_HOST} \.cn [NC,OR] RewriteCond %{REMOTE_HOST} \.in [NC,OR] RewriteCond %{REMOTE_HOST} \.de [NC,OR] RewriteCond %{REMOTE_HOST} \.cz [NC,OR] RewriteCond %{REMOTE_HOST} \.kp [NC,OR] RewriteCond %{REMOTE_HOST} \.kr [NC,OR] RewriteCond %{REMOTE_HOST} \.ng [NC,OR] RewriteCond %{REMOTE_HOST} \.pk [NC] RewriteRule .* - [F] # NOW PLACE YOUR OTHER REWRITE RULES YOU MAY HAVE HERE. # ВКЛЮЧИТЬ РЕКЛАМНЫЕ ПРАВИЛА # I HAVE NO FREAKING IDEA WHAT THIS DOES, BUT CPANEL AUTOMATICALLY CREATES IT <Files 403.shtml> order allow,deny allow from all </Files> # THIS IS FOR FUTURE EXPANSION -- I CAN DENY BY INDIVIDUAL IP ADDRESSES HERE, # OR I CAN ALLOW CERTAIN IP ADDRESS HERE. I CANNOT, HOWEVER, ADD DOMAIN TLDS LIKE # .ru HERE BECAUSE OF THE REVERSE DNS SLOWDOWN WITH THIS WEB HOSTING PROVIDER. # FOR THAT, I USE THE REWRITE RULES BELOW. <Limit GET HEAD POST> order deny,allow </Limit> # THIS IS IMPORTANT. WHAT IT DOES IS LOOK AT ALL THE OTHER HTTP TYPE OF ACTIVITIES # LIKE WEBDAV (A SECURITY HOLE, POTENTIALLY) AND BLOCK THOSE, LEAVING ONLY NORMAL # BROWSER STUFF WHICH IS ALWAYS POST, HEAD, AND GET. <LimitExcept POST HEAD GET> deny from all </LimitExcept> # TURN ON REWRITE RULES RewriteEngine on # CHECK THE HOST NAME SENT BY THE BROWSER AND BLOCK IT WITH 403 FORBIDDEN IF # FROM PARTICULAR COUNTRIES. RewriteCond %{REMOTE_HOST} \.ru [NC,OR] RewriteCond %{REMOTE_HOST} \.cn [NC,OR] RewriteCond %{REMOTE_HOST} \.in [NC,OR] RewriteCond %{REMOTE_HOST} \.de [NC,OR] RewriteCond %{REMOTE_HOST} \.cz [NC,OR] RewriteCond %{REMOTE_HOST} \.kp [NC,OR] RewriteCond %{REMOTE_HOST} \.kr [NC,OR] RewriteCond %{REMOTE_HOST} \.ng [NC,OR] RewriteCond %{REMOTE_HOST} \.pk [NC] RewriteRule .* - [F] # NOW PLACE YOUR OTHER REWRITE RULES YOU MAY HAVE HERE. # ПРОВЕРЬТЕ ИМЯ ХОЗЯЙСТВА, ПОСВЯТЬ БРОШЕРОМ И БЛОКОМ С 403 ЗАПРЕЩАЕТСЯ, ЕСЛИ # I HAVE NO FREAKING IDEA WHAT THIS DOES, BUT CPANEL AUTOMATICALLY CREATES IT <Files 403.shtml> order allow,deny allow from all </Files> # THIS IS FOR FUTURE EXPANSION -- I CAN DENY BY INDIVIDUAL IP ADDRESSES HERE, # OR I CAN ALLOW CERTAIN IP ADDRESS HERE. I CANNOT, HOWEVER, ADD DOMAIN TLDS LIKE # .ru HERE BECAUSE OF THE REVERSE DNS SLOWDOWN WITH THIS WEB HOSTING PROVIDER. # FOR THAT, I USE THE REWRITE RULES BELOW. <Limit GET HEAD POST> order deny,allow </Limit> # THIS IS IMPORTANT. WHAT IT DOES IS LOOK AT ALL THE OTHER HTTP TYPE OF ACTIVITIES # LIKE WEBDAV (A SECURITY HOLE, POTENTIALLY) AND BLOCK THOSE, LEAVING ONLY NORMAL # BROWSER STUFF WHICH IS ALWAYS POST, HEAD, AND GET. <LimitExcept POST HEAD GET> deny from all </LimitExcept> # TURN ON REWRITE RULES RewriteEngine on # CHECK THE HOST NAME SENT BY THE BROWSER AND BLOCK IT WITH 403 FORBIDDEN IF # FROM PARTICULAR COUNTRIES. RewriteCond %{REMOTE_HOST} \.ru [NC,OR] RewriteCond %{REMOTE_HOST} \.cn [NC,OR] RewriteCond %{REMOTE_HOST} \.in [NC,OR] RewriteCond %{REMOTE_HOST} \.de [NC,OR] RewriteCond %{REMOTE_HOST} \.cz [NC,OR] RewriteCond %{REMOTE_HOST} \.kp [NC,OR] RewriteCond %{REMOTE_HOST} \.kr [NC,OR] RewriteCond %{REMOTE_HOST} \.ng [NC,OR] RewriteCond %{REMOTE_HOST} \.pk [NC] RewriteRule .* - [F] # NOW PLACE YOUR OTHER REWRITE RULES YOU MAY HAVE HERE. # ИЗ ОСОБЫХ СТРАН. # I HAVE NO FREAKING IDEA WHAT THIS DOES, BUT CPANEL AUTOMATICALLY CREATES IT <Files 403.shtml> order allow,deny allow from all </Files> # THIS IS FOR FUTURE EXPANSION -- I CAN DENY BY INDIVIDUAL IP ADDRESSES HERE, # OR I CAN ALLOW CERTAIN IP ADDRESS HERE. I CANNOT, HOWEVER, ADD DOMAIN TLDS LIKE # .ru HERE BECAUSE OF THE REVERSE DNS SLOWDOWN WITH THIS WEB HOSTING PROVIDER. # FOR THAT, I USE THE REWRITE RULES BELOW. <Limit GET HEAD POST> order deny,allow </Limit> # THIS IS IMPORTANT. WHAT IT DOES IS LOOK AT ALL THE OTHER HTTP TYPE OF ACTIVITIES # LIKE WEBDAV (A SECURITY HOLE, POTENTIALLY) AND BLOCK THOSE, LEAVING ONLY NORMAL # BROWSER STUFF WHICH IS ALWAYS POST, HEAD, AND GET. <LimitExcept POST HEAD GET> deny from all </LimitExcept> # TURN ON REWRITE RULES RewriteEngine on # CHECK THE HOST NAME SENT BY THE BROWSER AND BLOCK IT WITH 403 FORBIDDEN IF # FROM PARTICULAR COUNTRIES. RewriteCond %{REMOTE_HOST} \.ru [NC,OR] RewriteCond %{REMOTE_HOST} \.cn [NC,OR] RewriteCond %{REMOTE_HOST} \.in [NC,OR] RewriteCond %{REMOTE_HOST} \.de [NC,OR] RewriteCond %{REMOTE_HOST} \.cz [NC,OR] RewriteCond %{REMOTE_HOST} \.kp [NC,OR] RewriteCond %{REMOTE_HOST} \.kr [NC,OR] RewriteCond %{REMOTE_HOST} \.ng [NC,OR] RewriteCond %{REMOTE_HOST} \.pk [NC] RewriteRule .* - [F] # NOW PLACE YOUR OTHER REWRITE RULES YOU MAY HAVE HERE. RewriteCond% {REMOTE_HOST} \ .ru [NC, OR] # I HAVE NO FREAKING IDEA WHAT THIS DOES, BUT CPANEL AUTOMATICALLY CREATES IT <Files 403.shtml> order allow,deny allow from all </Files> # THIS IS FOR FUTURE EXPANSION -- I CAN DENY BY INDIVIDUAL IP ADDRESSES HERE, # OR I CAN ALLOW CERTAIN IP ADDRESS HERE. I CANNOT, HOWEVER, ADD DOMAIN TLDS LIKE # .ru HERE BECAUSE OF THE REVERSE DNS SLOWDOWN WITH THIS WEB HOSTING PROVIDER. # FOR THAT, I USE THE REWRITE RULES BELOW. <Limit GET HEAD POST> order deny,allow </Limit> # THIS IS IMPORTANT. WHAT IT DOES IS LOOK AT ALL THE OTHER HTTP TYPE OF ACTIVITIES # LIKE WEBDAV (A SECURITY HOLE, POTENTIALLY) AND BLOCK THOSE, LEAVING ONLY NORMAL # BROWSER STUFF WHICH IS ALWAYS POST, HEAD, AND GET. <LimitExcept POST HEAD GET> deny from all </LimitExcept> # TURN ON REWRITE RULES RewriteEngine on # CHECK THE HOST NAME SENT BY THE BROWSER AND BLOCK IT WITH 403 FORBIDDEN IF # FROM PARTICULAR COUNTRIES. RewriteCond %{REMOTE_HOST} \.ru [NC,OR] RewriteCond %{REMOTE_HOST} \.cn [NC,OR] RewriteCond %{REMOTE_HOST} \.in [NC,OR] RewriteCond %{REMOTE_HOST} \.de [NC,OR] RewriteCond %{REMOTE_HOST} \.cz [NC,OR] RewriteCond %{REMOTE_HOST} \.kp [NC,OR] RewriteCond %{REMOTE_HOST} \.kr [NC,OR] RewriteCond %{REMOTE_HOST} \.ng [NC,OR] RewriteCond %{REMOTE_HOST} \.pk [NC] RewriteRule .* - [F] # NOW PLACE YOUR OTHER REWRITE RULES YOU MAY HAVE HERE. RewriteCond% {REMOTE_HOST} \ .cn [NC, OR] # I HAVE NO FREAKING IDEA WHAT THIS DOES, BUT CPANEL AUTOMATICALLY CREATES IT <Files 403.shtml> order allow,deny allow from all </Files> # THIS IS FOR FUTURE EXPANSION -- I CAN DENY BY INDIVIDUAL IP ADDRESSES HERE, # OR I CAN ALLOW CERTAIN IP ADDRESS HERE. I CANNOT, HOWEVER, ADD DOMAIN TLDS LIKE # .ru HERE BECAUSE OF THE REVERSE DNS SLOWDOWN WITH THIS WEB HOSTING PROVIDER. # FOR THAT, I USE THE REWRITE RULES BELOW. <Limit GET HEAD POST> order deny,allow </Limit> # THIS IS IMPORTANT. WHAT IT DOES IS LOOK AT ALL THE OTHER HTTP TYPE OF ACTIVITIES # LIKE WEBDAV (A SECURITY HOLE, POTENTIALLY) AND BLOCK THOSE, LEAVING ONLY NORMAL # BROWSER STUFF WHICH IS ALWAYS POST, HEAD, AND GET. <LimitExcept POST HEAD GET> deny from all </LimitExcept> # TURN ON REWRITE RULES RewriteEngine on # CHECK THE HOST NAME SENT BY THE BROWSER AND BLOCK IT WITH 403 FORBIDDEN IF # FROM PARTICULAR COUNTRIES. RewriteCond %{REMOTE_HOST} \.ru [NC,OR] RewriteCond %{REMOTE_HOST} \.cn [NC,OR] RewriteCond %{REMOTE_HOST} \.in [NC,OR] RewriteCond %{REMOTE_HOST} \.de [NC,OR] RewriteCond %{REMOTE_HOST} \.cz [NC,OR] RewriteCond %{REMOTE_HOST} \.kp [NC,OR] RewriteCond %{REMOTE_HOST} \.kr [NC,OR] RewriteCond %{REMOTE_HOST} \.ng [NC,OR] RewriteCond %{REMOTE_HOST} \.pk [NC] RewriteRule .* - [F] # NOW PLACE YOUR OTHER REWRITE RULES YOU MAY HAVE HERE. RewriteCond% {REMOTE_HOST} \ .in [NC, OR] # I HAVE NO FREAKING IDEA WHAT THIS DOES, BUT CPANEL AUTOMATICALLY CREATES IT <Files 403.shtml> order allow,deny allow from all </Files> # THIS IS FOR FUTURE EXPANSION -- I CAN DENY BY INDIVIDUAL IP ADDRESSES HERE, # OR I CAN ALLOW CERTAIN IP ADDRESS HERE. I CANNOT, HOWEVER, ADD DOMAIN TLDS LIKE # .ru HERE BECAUSE OF THE REVERSE DNS SLOWDOWN WITH THIS WEB HOSTING PROVIDER. # FOR THAT, I USE THE REWRITE RULES BELOW. <Limit GET HEAD POST> order deny,allow </Limit> # THIS IS IMPORTANT. WHAT IT DOES IS LOOK AT ALL THE OTHER HTTP TYPE OF ACTIVITIES # LIKE WEBDAV (A SECURITY HOLE, POTENTIALLY) AND BLOCK THOSE, LEAVING ONLY NORMAL # BROWSER STUFF WHICH IS ALWAYS POST, HEAD, AND GET. <LimitExcept POST HEAD GET> deny from all </LimitExcept> # TURN ON REWRITE RULES RewriteEngine on # CHECK THE HOST NAME SENT BY THE BROWSER AND BLOCK IT WITH 403 FORBIDDEN IF # FROM PARTICULAR COUNTRIES. RewriteCond %{REMOTE_HOST} \.ru [NC,OR] RewriteCond %{REMOTE_HOST} \.cn [NC,OR] RewriteCond %{REMOTE_HOST} \.in [NC,OR] RewriteCond %{REMOTE_HOST} \.de [NC,OR] RewriteCond %{REMOTE_HOST} \.cz [NC,OR] RewriteCond %{REMOTE_HOST} \.kp [NC,OR] RewriteCond %{REMOTE_HOST} \.kr [NC,OR] RewriteCond %{REMOTE_HOST} \.ng [NC,OR] RewriteCond %{REMOTE_HOST} \.pk [NC] RewriteRule .* - [F] # NOW PLACE YOUR OTHER REWRITE RULES YOU MAY HAVE HERE. RewriteCond% {REMOTE_HOST} \ .de [NC, OR] # I HAVE NO FREAKING IDEA WHAT THIS DOES, BUT CPANEL AUTOMATICALLY CREATES IT <Files 403.shtml> order allow,deny allow from all </Files> # THIS IS FOR FUTURE EXPANSION -- I CAN DENY BY INDIVIDUAL IP ADDRESSES HERE, # OR I CAN ALLOW CERTAIN IP ADDRESS HERE. I CANNOT, HOWEVER, ADD DOMAIN TLDS LIKE # .ru HERE BECAUSE OF THE REVERSE DNS SLOWDOWN WITH THIS WEB HOSTING PROVIDER. # FOR THAT, I USE THE REWRITE RULES BELOW. <Limit GET HEAD POST> order deny,allow </Limit> # THIS IS IMPORTANT. WHAT IT DOES IS LOOK AT ALL THE OTHER HTTP TYPE OF ACTIVITIES # LIKE WEBDAV (A SECURITY HOLE, POTENTIALLY) AND BLOCK THOSE, LEAVING ONLY NORMAL # BROWSER STUFF WHICH IS ALWAYS POST, HEAD, AND GET. <LimitExcept POST HEAD GET> deny from all </LimitExcept> # TURN ON REWRITE RULES RewriteEngine on # CHECK THE HOST NAME SENT BY THE BROWSER AND BLOCK IT WITH 403 FORBIDDEN IF # FROM PARTICULAR COUNTRIES. RewriteCond %{REMOTE_HOST} \.ru [NC,OR] RewriteCond %{REMOTE_HOST} \.cn [NC,OR] RewriteCond %{REMOTE_HOST} \.in [NC,OR] RewriteCond %{REMOTE_HOST} \.de [NC,OR] RewriteCond %{REMOTE_HOST} \.cz [NC,OR] RewriteCond %{REMOTE_HOST} \.kp [NC,OR] RewriteCond %{REMOTE_HOST} \.kr [NC,OR] RewriteCond %{REMOTE_HOST} \.ng [NC,OR] RewriteCond %{REMOTE_HOST} \.pk [NC] RewriteRule .* - [F] # NOW PLACE YOUR OTHER REWRITE RULES YOU MAY HAVE HERE. RewriteCond% {REMOTE_HOST} \ .cz [NC, OR] # I HAVE NO FREAKING IDEA WHAT THIS DOES, BUT CPANEL AUTOMATICALLY CREATES IT <Files 403.shtml> order allow,deny allow from all </Files> # THIS IS FOR FUTURE EXPANSION -- I CAN DENY BY INDIVIDUAL IP ADDRESSES HERE, # OR I CAN ALLOW CERTAIN IP ADDRESS HERE. I CANNOT, HOWEVER, ADD DOMAIN TLDS LIKE # .ru HERE BECAUSE OF THE REVERSE DNS SLOWDOWN WITH THIS WEB HOSTING PROVIDER. # FOR THAT, I USE THE REWRITE RULES BELOW. <Limit GET HEAD POST> order deny,allow </Limit> # THIS IS IMPORTANT. WHAT IT DOES IS LOOK AT ALL THE OTHER HTTP TYPE OF ACTIVITIES # LIKE WEBDAV (A SECURITY HOLE, POTENTIALLY) AND BLOCK THOSE, LEAVING ONLY NORMAL # BROWSER STUFF WHICH IS ALWAYS POST, HEAD, AND GET. <LimitExcept POST HEAD GET> deny from all </LimitExcept> # TURN ON REWRITE RULES RewriteEngine on # CHECK THE HOST NAME SENT BY THE BROWSER AND BLOCK IT WITH 403 FORBIDDEN IF # FROM PARTICULAR COUNTRIES. RewriteCond %{REMOTE_HOST} \.ru [NC,OR] RewriteCond %{REMOTE_HOST} \.cn [NC,OR] RewriteCond %{REMOTE_HOST} \.in [NC,OR] RewriteCond %{REMOTE_HOST} \.de [NC,OR] RewriteCond %{REMOTE_HOST} \.cz [NC,OR] RewriteCond %{REMOTE_HOST} \.kp [NC,OR] RewriteCond %{REMOTE_HOST} \.kr [NC,OR] RewriteCond %{REMOTE_HOST} \.ng [NC,OR] RewriteCond %{REMOTE_HOST} \.pk [NC] RewriteRule .* - [F] # NOW PLACE YOUR OTHER REWRITE RULES YOU MAY HAVE HERE. RewriteCond% {REMOTE_HOST} \ .kp [NC, OR] # I HAVE NO FREAKING IDEA WHAT THIS DOES, BUT CPANEL AUTOMATICALLY CREATES IT <Files 403.shtml> order allow,deny allow from all </Files> # THIS IS FOR FUTURE EXPANSION -- I CAN DENY BY INDIVIDUAL IP ADDRESSES HERE, # OR I CAN ALLOW CERTAIN IP ADDRESS HERE. I CANNOT, HOWEVER, ADD DOMAIN TLDS LIKE # .ru HERE BECAUSE OF THE REVERSE DNS SLOWDOWN WITH THIS WEB HOSTING PROVIDER. # FOR THAT, I USE THE REWRITE RULES BELOW. <Limit GET HEAD POST> order deny,allow </Limit> # THIS IS IMPORTANT. WHAT IT DOES IS LOOK AT ALL THE OTHER HTTP TYPE OF ACTIVITIES # LIKE WEBDAV (A SECURITY HOLE, POTENTIALLY) AND BLOCK THOSE, LEAVING ONLY NORMAL # BROWSER STUFF WHICH IS ALWAYS POST, HEAD, AND GET. <LimitExcept POST HEAD GET> deny from all </LimitExcept> # TURN ON REWRITE RULES RewriteEngine on # CHECK THE HOST NAME SENT BY THE BROWSER AND BLOCK IT WITH 403 FORBIDDEN IF # FROM PARTICULAR COUNTRIES. RewriteCond %{REMOTE_HOST} \.ru [NC,OR] RewriteCond %{REMOTE_HOST} \.cn [NC,OR] RewriteCond %{REMOTE_HOST} \.in [NC,OR] RewriteCond %{REMOTE_HOST} \.de [NC,OR] RewriteCond %{REMOTE_HOST} \.cz [NC,OR] RewriteCond %{REMOTE_HOST} \.kp [NC,OR] RewriteCond %{REMOTE_HOST} \.kr [NC,OR] RewriteCond %{REMOTE_HOST} \.ng [NC,OR] RewriteCond %{REMOTE_HOST} \.pk [NC] RewriteRule .* - [F] # NOW PLACE YOUR OTHER REWRITE RULES YOU MAY HAVE HERE. RewriteCond% {REMOTE_HOST} \ .kr [NC, OR] # I HAVE NO FREAKING IDEA WHAT THIS DOES, BUT CPANEL AUTOMATICALLY CREATES IT <Files 403.shtml> order allow,deny allow from all </Files> # THIS IS FOR FUTURE EXPANSION -- I CAN DENY BY INDIVIDUAL IP ADDRESSES HERE, # OR I CAN ALLOW CERTAIN IP ADDRESS HERE. I CANNOT, HOWEVER, ADD DOMAIN TLDS LIKE # .ru HERE BECAUSE OF THE REVERSE DNS SLOWDOWN WITH THIS WEB HOSTING PROVIDER. # FOR THAT, I USE THE REWRITE RULES BELOW. <Limit GET HEAD POST> order deny,allow </Limit> # THIS IS IMPORTANT. WHAT IT DOES IS LOOK AT ALL THE OTHER HTTP TYPE OF ACTIVITIES # LIKE WEBDAV (A SECURITY HOLE, POTENTIALLY) AND BLOCK THOSE, LEAVING ONLY NORMAL # BROWSER STUFF WHICH IS ALWAYS POST, HEAD, AND GET. <LimitExcept POST HEAD GET> deny from all </LimitExcept> # TURN ON REWRITE RULES RewriteEngine on # CHECK THE HOST NAME SENT BY THE BROWSER AND BLOCK IT WITH 403 FORBIDDEN IF # FROM PARTICULAR COUNTRIES. RewriteCond %{REMOTE_HOST} \.ru [NC,OR] RewriteCond %{REMOTE_HOST} \.cn [NC,OR] RewriteCond %{REMOTE_HOST} \.in [NC,OR] RewriteCond %{REMOTE_HOST} \.de [NC,OR] RewriteCond %{REMOTE_HOST} \.cz [NC,OR] RewriteCond %{REMOTE_HOST} \.kp [NC,OR] RewriteCond %{REMOTE_HOST} \.kr [NC,OR] RewriteCond %{REMOTE_HOST} \.ng [NC,OR] RewriteCond %{REMOTE_HOST} \.pk [NC] RewriteRule .* - [F] # NOW PLACE YOUR OTHER REWRITE RULES YOU MAY HAVE HERE. RewriteCond% {REMOTE_HOST} \ .ng [NC, OR] # I HAVE NO FREAKING IDEA WHAT THIS DOES, BUT CPANEL AUTOMATICALLY CREATES IT <Files 403.shtml> order allow,deny allow from all </Files> # THIS IS FOR FUTURE EXPANSION -- I CAN DENY BY INDIVIDUAL IP ADDRESSES HERE, # OR I CAN ALLOW CERTAIN IP ADDRESS HERE. I CANNOT, HOWEVER, ADD DOMAIN TLDS LIKE # .ru HERE BECAUSE OF THE REVERSE DNS SLOWDOWN WITH THIS WEB HOSTING PROVIDER. # FOR THAT, I USE THE REWRITE RULES BELOW. <Limit GET HEAD POST> order deny,allow </Limit> # THIS IS IMPORTANT. WHAT IT DOES IS LOOK AT ALL THE OTHER HTTP TYPE OF ACTIVITIES # LIKE WEBDAV (A SECURITY HOLE, POTENTIALLY) AND BLOCK THOSE, LEAVING ONLY NORMAL # BROWSER STUFF WHICH IS ALWAYS POST, HEAD, AND GET. <LimitExcept POST HEAD GET> deny from all </LimitExcept> # TURN ON REWRITE RULES RewriteEngine on # CHECK THE HOST NAME SENT BY THE BROWSER AND BLOCK IT WITH 403 FORBIDDEN IF # FROM PARTICULAR COUNTRIES. RewriteCond %{REMOTE_HOST} \.ru [NC,OR] RewriteCond %{REMOTE_HOST} \.cn [NC,OR] RewriteCond %{REMOTE_HOST} \.in [NC,OR] RewriteCond %{REMOTE_HOST} \.de [NC,OR] RewriteCond %{REMOTE_HOST} \.cz [NC,OR] RewriteCond %{REMOTE_HOST} \.kp [NC,OR] RewriteCond %{REMOTE_HOST} \.kr [NC,OR] RewriteCond %{REMOTE_HOST} \.ng [NC,OR] RewriteCond %{REMOTE_HOST} \.pk [NC] RewriteRule .* - [F] # NOW PLACE YOUR OTHER REWRITE RULES YOU MAY HAVE HERE. RewriteCond% {REMOTE_HOST} \ .pk [NC] # I HAVE NO FREAKING IDEA WHAT THIS DOES, BUT CPANEL AUTOMATICALLY CREATES IT <Files 403.shtml> order allow,deny allow from all </Files> # THIS IS FOR FUTURE EXPANSION -- I CAN DENY BY INDIVIDUAL IP ADDRESSES HERE, # OR I CAN ALLOW CERTAIN IP ADDRESS HERE. I CANNOT, HOWEVER, ADD DOMAIN TLDS LIKE # .ru HERE BECAUSE OF THE REVERSE DNS SLOWDOWN WITH THIS WEB HOSTING PROVIDER. # FOR THAT, I USE THE REWRITE RULES BELOW. <Limit GET HEAD POST> order deny,allow </Limit> # THIS IS IMPORTANT. WHAT IT DOES IS LOOK AT ALL THE OTHER HTTP TYPE OF ACTIVITIES # LIKE WEBDAV (A SECURITY HOLE, POTENTIALLY) AND BLOCK THOSE, LEAVING ONLY NORMAL # BROWSER STUFF WHICH IS ALWAYS POST, HEAD, AND GET. <LimitExcept POST HEAD GET> deny from all </LimitExcept> # TURN ON REWRITE RULES RewriteEngine on # CHECK THE HOST NAME SENT BY THE BROWSER AND BLOCK IT WITH 403 FORBIDDEN IF # FROM PARTICULAR COUNTRIES. RewriteCond %{REMOTE_HOST} \.ru [NC,OR] RewriteCond %{REMOTE_HOST} \.cn [NC,OR] RewriteCond %{REMOTE_HOST} \.in [NC,OR] RewriteCond %{REMOTE_HOST} \.de [NC,OR] RewriteCond %{REMOTE_HOST} \.cz [NC,OR] RewriteCond %{REMOTE_HOST} \.kp [NC,OR] RewriteCond %{REMOTE_HOST} \.kr [NC,OR] RewriteCond %{REMOTE_HOST} \.ng [NC,OR] RewriteCond %{REMOTE_HOST} \.pk [NC] RewriteRule .* - [F] # NOW PLACE YOUR OTHER REWRITE RULES YOU MAY HAVE HERE. 
  • Вычисление и выставление счетов за использование многоадресной рассылки IP в Интерlessе
  • Для типичного широкополосного интерless-провайдера узлы в одной подсети маршрутизируются вместе или они соединяются?
  • Нумерация classа TC / filterа Linux
  • Какое оборудование действительно использует интерless-провайдер?
  • Каковы шаги при планировании перехода от одного провайдера к другому?
  • Ошибка геолокации Google DNS
  • Только в состоянии использовать первый IP-адрес в rangeе от ISP
  • Как настроить публичный статический IP-адрес в Ubuntu 9.10
  • Я изменил ISP, теперь www доступ к моему websiteу не работает, но HTTP-это
  • Оборудование для резервирования ISP
  • Концептуальный: реселлинг услуг интерless-провайдера (vISP?)
  • Interesting Posts

    Apache Kerberos / LDAP: не удалось прочитать требуемый inputной параметр: было указано недопустимое имя (, Неизвестная ошибка)

    Cisco ASA – вkeyение связи между тем же уровнем безопасности

    выполнение службы после запуска другой службы

    Как заблокировать Ip в .httaccess на Apache 2.4

    Поддерживает ли database Postgres дифференциальное резервное копирование

    Подkeyите Linux-машину к активному directoryу Windows

    Как назначить несколько адресов IPv6 с помощью DHCPv6 на один interface?

    Планирование обновлений на Windows Server 2016

    Проблемы подkeyения к локальной сети LAN

    Клонировать, а затем маршрутизировать SNMP-ловушки в новый пункт назначения

    Отдельная папка NFS, совместно используемая несколькими клиентами

    Windows Server 2003 – Назначение IP-адреса различным программам

    Все хосты ESX4 не отвечают после перезагрузки serverа vCenter

    SR-IOV на гостевом гостевом компьютере KVM с использованием отмеченных vlans

    Масштабирование stackа LAMP

    Давайте будем гением компьютера.