Document the Under Attack Mode UI - #207
Open
DexterIA wants to merge 2 commits into
Open
Conversation
Add a WebShield section to the Admin Interface and to the User Interface, covering the Under Attack Mode tab: the service switches, the URL tester, the rules table, the rule dialog and its path scoping, and how an administrator sees the rules that belong to end users. The tab is gated on WebShield feature availability, so the section leads with why it may be absent (LiteSpeed cPanel) and how to check with imunify360-wsctl filters. The WebShield subsection under Settings is renamed to "WebShield settings": the new section owns the #webshield anchor, and a stable name is preferable to the positional #webshield-2 VuePress would assign. It also gains a note that those options do not control Under Attack Mode. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The new UI sections link into this page, so the parts they rely on had drifted from what the agent and wafd actually accept: - site owners can manage rules for their own domains once the admin enables the visibility switch; document the switch, the OWNER column and the --owner filters - domains accept a leading wildcard (*.example.com matches subdomains only, .example.com matches both) - path matchers also support wildcard, query_contains and query_regex, and are applied to the whole URI including the query string - whitelisted IP addresses are never challenged - Enable WebShield in Settings does not control UAM Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
cl-vkuznetsov
approved these changes
Aug 27, 2026
DexterIA
marked this pull request as ready for review
August 27, 2026 12:07
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents the WebShield Under Attack Mode user interface. The feature already had a CLI-oriented page at /features/under_attack_mode/; this adds the UI half and links the two together instead of duplicating the description.
Admin Interface — a new ## WebShield section with an ### Under Attack Mode subsection: the service switches, the URL tester, the rules table, the rule dialog, path scoping with the full condition table, and how an administrator sees rules owned by end users. The WebShield → Under Attack Mode nesting leaves room for the further WebShield tabs that are coming.
User Interface — the same structure for site owners, shorter, pointing at the admin section and the feature page for the details.
Under Attack Mode (UAM) feature page — brought in line with WebShield 1.47, since the new UI sections link into it: site-owner support and the visibility switch, domain wildcards, the wildcard / query_contains / query_regex matchers, query-string matching semantics, and the whitelist bypass.
10 screenshots taken on a cPanel + AlmaLinux 10 test server (imunify360 8.14.0, imunify-ui 8.13.0, imunify360-webshield-bundle 1.47.0). The matching semantics documented here were verified on that server with imunify360-wsctl uam test.