Как прибить POST HTTP/1.1
Как прибить ботов с помощью Nginx без парсинга логов: 2.134.162.100 - - [08/Jul/2014:14:54:34 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:34 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:34 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:34 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:34 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:34 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:34 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:34 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:35 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:35 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:35 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:35 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:35 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:35 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:35 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:36 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:36 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:36 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:36 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:36 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:36 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:37 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:37 +0200] POST HTTP/1.1 400 166 - - 177.55.241.91 - - [08/Jul/2014:14:54:38 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:38 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:38 +0200] POST HTTP/1.1 400 166 - - 177.55.241.91 - - [08/Jul/2014:14:54:38 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.105.91 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.105.91 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.105.91 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.105.91 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 197.162.105.91 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 197.162.105.91 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 93.77.24.242 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 93.77.24.242 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 197.162.105.91 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 93.77.24.242 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 197.162.105.91 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 93.77.24.242 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 37.45.201.168 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:41 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:41 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:41 +0200] POST HTTP/1.1 400 166 - - 93.77.24.242 - - [08/Jul/2014:14:54:41 +0200] POST HTTP/1.1 400 166 - - 93.77.24.242 - - [08/Jul/2014:14:54:41 +0200] POST HTTP/1.1 400 166 - - 93.77.24.242 - - [08/Jul/2014:14:54:41 +0200] POST HTTP/1.1 400 166 - - Такое не помогло: if ($request_method = POST){ return 499; } Posted at Nginx Forum: http://forum.nginx.org/read.php?21,251542,251542#msg-251542
nginx-1.7.3
Изменения в nginx 1.7.3 08.07.2014 *) Добавление: weak entity tags теперь не удаляются при изменениях ответа, а strong entity tags преобразуются в weak. *) Добавление: ревалидация элементов кэша теперь, если это возможно, использует заголовок If-None-Match. *) Добавление: директива ssl_password_file. *) Исправление: при возврате ответа из кэша заголовок запроса If-None-Match игнорировался, если в ответе не было заголовка Last-Modified. *) Исправление: сообщения peer closed connection in SSL handshake при соединении с бэкендами логгировались на уровне info вместо error. *) Исправление: в модуле ngx_http_dav_module в nginx/Windows. *) Исправление: SPDY-соединения могли неожиданно закрываться, если использовалось кэширование. -- Maxim Dounin http://nginx.org/en/donation.html ___ nginx-ru mailing list nginx-ru@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx-ru
Re: SPDY вместе с включенным proxy_cache_bypass (#428)
On Jul 7, 2014, at 1:00 PM, Maxim Konovalov ma...@nginx.com wrote: On 6/17/14 5:57 PM, Maxim Konovalov wrote: On 6/17/14 5:54 PM, Anatoly Mikhailov wrote: On 06 Jun 2014, at 16:13, Anatoly Mikhailov anat...@sonru.com wrote: On 06 Jun 2014, at 14:27, Maxim Konovalov ma...@nginx.com wrote: [...] начал ловить те же баги на не пропатченном Nginx на другом сервере с меньшей нагрузкой, этот патч в опен-сорсе очень бы не помешал! Код в процессе внутреннего ревью. Отличная новость в пятницу, спасибо! Nginx 1.7.2 содержит именно этот багфикс? Не содержит. JFYI, 1.7.3, выпуск которого назначен на завтра, будет с фиксом: http://mailman.nginx.org/pipermail/nginx-devel/2014-July/005540.html http://trac.nginx.org/nginx/ticket/428 Супер, спасибо! Также здесь решен вопрос с weak etags, золотой релиз! :) -- Maxim Konovalov http://nginx.com ___ nginx-ru mailing list nginx-ru@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx-ru ___ nginx-ru mailing list nginx-ru@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx-ru
Re: Как прибить POST HTTP/1.1
error_page 400 =444; ? 2014-07-08 19:19 GMT+06:00 lisua nginx-fo...@nginx.us: Как прибить ботов с помощью Nginx без парсинга логов: 2.134.162.100 - - [08/Jul/2014:14:54:34 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:34 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:34 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:34 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:34 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:34 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:34 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:34 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:35 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:35 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:35 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:35 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:35 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:35 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:35 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:36 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:36 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:36 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:36 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:36 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:36 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:37 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:37 +0200] POST HTTP/1.1 400 166 - - 177.55.241.91 - - [08/Jul/2014:14:54:38 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:38 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:38 +0200] POST HTTP/1.1 400 166 - - 177.55.241.91 - - [08/Jul/2014:14:54:38 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.105.91 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.105.91 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.105.91 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.105.91 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 197.162.105.91 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 197.162.105.91 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 93.77.24.242 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 93.77.24.242 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 197.162.105.91 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 93.77.24.242 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 197.162.105.91 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 93.77.24.242 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 37.45.201.168 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:41 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:41 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:41 +0200] POST HTTP/1.1 400 166 - - 93.77.24.242 - - [08/Jul/2014:14:54:41 +0200] POST HTTP/1.1 400 166 - - 93.77.24.242 - - [08/Jul/2014:14:54:41 +0200] POST HTTP/1.1 400 166 - - 93.77.24.242 - - [08/Jul/2014:14:54:41 +0200] POST
Re: nginx-1.7.3
Добавление: ревалидация элементов кэша теперь, если это возможно, использует заголовок If-None-Match. Отлично, спасибо! Когда появится данная версия в ваших пакетах для CentOS 6? В http://nginx.org/packages/mainline/centos/6/ её ещё нет. Кстати можно уже создавать новую папку (http://nginx.org/packages/mainline/centos/7/) для пакетов CentOS 7, на днях был релиз данной OS. Posted at Nginx Forum: http://forum.nginx.org/read.php?21,251548,251553#msg-251553 ___ nginx-ru mailing list nginx-ru@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx-ru
Re: Как прибить POST HTTP/1.1
Я сделал одну зону с ограничением на кол-во запросов в секунду для GET и другую для POST. Второе ограничение, разумеется, жощщще. От пионеров помогает. set $binary_remote_addr_post ; if ($request_method = POST) { set $binary_remote_addr_post $binary_remote_addr; } limit_req_zone $binary_remote_addr zone=IPRATELIMIT:20m rate=20r/s; limit_req_zone $binary_remote_addr_post zone=IPRATELIMIT_POST:20m rate=2r/s; Влад 08 июля 2014 г., в 17:19, lisua nginx-fo...@nginx.us написал(а): Как прибить ботов с помощью Nginx без парсинга логов: 2.134.162.100 - - [08/Jul/2014:14:54:34 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:34 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:34 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:34 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:34 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:34 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:34 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:34 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:35 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:35 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:35 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:35 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:35 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:35 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:35 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:36 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:36 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:36 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:36 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:36 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:36 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:37 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:37 +0200] POST HTTP/1.1 400 166 - - 177.55.241.91 - - [08/Jul/2014:14:54:38 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:38 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:38 +0200] POST HTTP/1.1 400 166 - - 177.55.241.91 - - [08/Jul/2014:14:54:38 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.105.91 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.105.91 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.105.91 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.105.91 - - [08/Jul/2014:14:54:39 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 197.162.13.111 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 197.162.105.91 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 2.134.162.100 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 197.162.105.91 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 93.77.24.242 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 93.77.24.242 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 197.162.105.91 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 93.77.24.242 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 197.162.105.91 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 93.77.24.242 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166 - - 37.45.201.168 - - [08/Jul/2014:14:54:40 +0200] POST HTTP/1.1 400 166
Re: Как прибить POST HTTP/1.1
Подскажите как составить фильтр на корректность GET/POST запросов для Nginx Posted at Nginx Forum: http://forum.nginx.org/read.php?21,251542,251557#msg-251557 ___ nginx-ru mailing list nginx-ru@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx-ru
Re: Как прибить POST HTTP/1.1
On Tuesday 08 July 2014 09:19:28 lisua wrote: Как прибить ботов с помощью Nginx без парсинга логов: 2.134.162.100 - - [08/Jul/2014:14:54:34 +0200] POST HTTP/1.1 400 166 - - [..] 93.77.24.242 - - [08/Jul/2014:14:54:41 +0200] POST HTTP/1.1 400 166 - - Такое не помогло: if ($request_method = POST){ return 499; } Из логов видно, что речи и вовсе не идет о POST запросе. Строчка POST HTTP/1.1 вообще не является корректным HTTP запросом. С тем же успехом они могли бы слать любой абстрактный набор байт, на который nginx и так сразу возвращает 400-ую ошибку. -- Валентин Бартенев ___ nginx-ru mailing list nginx-ru@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx-ru
Re: nginx-1.7.3
On 08 Jul 2014, at 19:32, S.A.N nginx-fo...@nginx.us wrote: Добавление: ревалидация элементов кэша теперь, если это возможно, использует заголовок If-None-Match. Отлично, спасибо! Когда появится данная версия в ваших пакетах для CentOS 6? В http://nginx.org/packages/mainline/centos/6/ её ещё нет. Уже. Кстати можно уже создавать новую папку (http://nginx.org/packages/mainline/centos/7/) для пакетов CentOS 7, на днях был релиз данной OS. Протестировать нужно. ___ nginx-ru mailing list nginx-ru@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx-ru