HTTP Flood

HTTP Flood prevents your system against attacks like HTTP Flood, Land Flood, Form Spoofing, Brute Force, Remote Site Scanners and many more on similar types. It was tested under limitless thread and distributed sources.

Please Attention!
1. This plugin blocks every flood like actions.
2. So don’t forget to deactivate the plugin before you do any fast moves e.g. sample data uploading…
3. If you banned your own site, you can re-enter only via change your ip address.

Arbitrary section

1- HTTP Connection Principle

Before connecting to a system running in the HTTP protocol, a data stream is generated between the server and the client called three way handshake.
Let’s first examine how a normal connection is established.

SYN
The client sends a SYN (Synchronize) packet that indicates that we want to connect to the server. The client and server must be compatible in order to establish a connection. The SYN package carries information about the client structure.

SYN + ACK
When the server receives the SYN packet, it analyzes the structure of the client and starts to wait for the client’s response by sending a SYN packet carrying information about the acknowledgment packet and the server structure, indicating an ACK (link acknowledgment).

ACK
When the client receives the SYN + ACK packet, it analyzes the structure of the server and sends a final ACK packet indicating that it satisfies the conditions required to establish the connection, and the data transfer starts by establishing a connection between the server and the client.

DATA TRANSFER

2- HTTP Flood Attack

So far we have examined the establishment of a normal HTTP connection.
Now let’s examine how the HTTP Flood attack works.

SYN
The client requests a connection by sending a SYN packet as if it were a normal connection request.

SYN + ACK
The server sends the SYN + ACK packet as if it were a regular connection request and waits for the client’s response.

SYN + 1
The client does not send the last ACK packet and the process repeats with a new SYN while the server is waiting for a response.

3- Protection Principle
We have seen the principle of normal connection and how these principles are manipulated to attack.
Finally, see how we provide security.

PERCEPTION
HTTP floods and derivative attacks occur at the application layer, not at the server layer like DDOS. We have developed a special algorithm that detects the attack parameters by examining the connection parameters.

DISCRIMINATION
Normal connection requests may continue to come in while the attack is ongoing, and a normal server should not remain unresponsive here. Our software distinguishes between attack requests and normal connection requests at this point.

BLOCK
The attack is detected in seconds and the attack source is notified to the server layer when the server is still able to respond to new connection requests. In this case, the attack source is blocked at the server layer and the server is not attacked.