Skip to main content
Version: 4.6.1

Repeated Request Block (BotManager Basic)

Repeated Request Block (BotManager Basic) protects the NetFUNNEL server from excessive traffic control API requests. When someone exceeds configured limits (too many requests per second or per interval), the server blocks their requests and returns 302 block responses.

What It Does​

Repeated Request Block monitors traffic control API requests to the NetFUNNEL server (Initial Entry Request, Re-entry Request, Alive Notice Request, Complete Request) and blocks IPs/IDs that exceed configured thresholds.

Important: This feature protects the NetFUNNEL server, not your customer service endpoints. It does not block bots or macros making requests to your application server.

How It Works​

When a request exceeds the configured limits:

  1. Block activated: Repeated Request Block is immediately activated for that IP/ID
  2. 302 response: The server returns 302 block responses for all requests during the block time
  3. Block screen: The NetFUNNEL agent displays the Repeated Request Block page to the user
  4. Auto-expires: After the block time expires, the IP/ID can make requests again

Key Features​

Policy Settings​

Configure blocking policies including:

  • Block type (IP, ID, or All)
  • Detecting interval and limit per interval
  • Limit per second
  • Block time

See Policy Settings for details.

User Management​

Manage lists to control blocking:

  • Temporary Block: View IPs/IDs currently blocked by policy settings
  • Unblock List: Allow specific IPs/IDs even if they exceed limits
  • Permanent Block List: Always block specific IPs/IDs
  • Whitelist: Completely bypass NetFUNNEL traffic control

See User Management for details.

Quick Start​

  1. Policy Settings: Configure blocking policies (start with default settings)
  2. User Management: Manage blocked IPs/IDs and lists as needed