xF2 Add-on XF Surge Guard

[Itnull]

XF Surge Guard reduces wasted XenForo load from unauthenticated guest and bot request patterns before they keep consuming PHP, MySQL, and XenForo resources.

It is built for a specific problem:

A guest, bot, crawler, scanner, or broken link repeatedly hits dynamic XenForo URLs that produce missing routes, 404s, permission failures, or other low-value responses. XenForo still has to boot, route, dispatch, query, and render a response for traffic that has already proven to be wasteful.

XF Surge Guard watches eligible unauthenticated requests and, in Guard mode, temporarily exports high-confidence waste patterns to a lightweight early bootstrap guard.

On later matching requests, the guard can answer before XenForo fully boots.

That means less wasted work for XenForo, PHP, and MySQL.

What it does​

XF Surge Guard observes eligible unauthenticated GET/HEAD requests and detects guest traffic waste such as:

• Soft 404 guest requests
• Missing dynamic XenForo paths
• Invalid route requests
• Failure-heavy guest traffic bursts
• Repeated bad-path requests
• Scanner-style probes and broken external links
• High-confidence request patterns that are safe to temporarily short-circuit

When a pattern qualifies, the add-on exports a short-lived rule to a lightweight early bootstrap guard loaded from XenForo’s src/config.php.

On later matching requests, the guard can return a tiny early response before XenForo performs expensive routing, controller dispatch, template rendering, session work, or database-heavy operations.

Simple example​

A guest requests:
/some-bad-url

XenForo boots normally and confirms the request is wasteful, such as a 404.

XF Surge Guard records the outcome.

If Guard mode is enabled, that guest request pattern can be temporarily managed.

The next matching guest request can then be answered early, before XenForo fully boots.

That means XenForo does not keep spending full application resources on the same disposable request pattern.

Operating modes​

• Disabled - no observation and no early enforcement.
• Observe - records and analyses eligible guest waste patterns, but does not answer anything early.
• Guard - enables short-lived early protection for currently managed waste patterns.

Observe mode is useful when you want to see what XF Surge Guard would manage before enabling early protection.Guard mode is where qualifying patterns can be temporarily answered before XenForo fully boots.


XF Surge Guard 1.0.4

Для просмотра скрытого содержимого вы должны войти или зарегистрироваться.