<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>DDoS on iMil.net</title>
    <link>http://imil.net/blog/tags/ddos/</link>
    <description>Recent content in DDoS on iMil.net</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 21 Mar 2020 07:01:41 +0100</lastBuildDate>
    <atom:link href="http://imil.net/blog/tags/ddos/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>HTTP flood drop with nginx</title>
      <link>http://imil.net/blog/posts/2020/http-flood-drop-with-nginx/</link>
      <pubDate>Sat, 21 Mar 2020 07:01:41 +0100</pubDate>
      <guid>http://imil.net/blog/posts/2020/http-flood-drop-with-nginx/</guid>
      <description>&lt;p&gt;The other day at &lt;code&gt;${DAYWORK}&lt;/code&gt; we got hit by a simple yet efficient &lt;em&gt;DDoS&lt;/em&gt; attack, basically, there were lots of regular &lt;code&gt;HTTP&lt;/code&gt; queries with a specific query parameter but using either &lt;code&gt;GET&lt;/code&gt;, &lt;code&gt;POST&lt;/code&gt; or &lt;code&gt;HEAD&lt;/code&gt; methods:&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;www.customer.com:443:80 174.76.48.233 - - [19/Mar/2020:17:26:11 +0000] &amp;#34;POST /?=Best_HTTP_Flooder_For_FREE_by_PassDDoS&amp;amp;9716 HTTP/1.0&amp;#34; 200 62861 &amp;#34;http://validator.w3.org/feed/check.cgi?url=https://www.customer.com&amp;#34; &#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Fortunately, the parameter was always the same, and as we use an &lt;a href=&#34;https://nginx.org&#34;&gt;nginx&lt;/a&gt; reverse proxy farm in front of our customer&amp;rsquo;s websites, we could deploy this simple trick in order to get rid of the attack:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
