From a71dc553dcc1fd345c25bfc0568a58e4bdcac2eb Mon Sep 17 00:00:00 2001 From: Dominik Matic Date: Thu, 17 Sep 2026 16:19:18 +0200 Subject: [PATCH] Update botstopper standard policy --- docs/hypernode-platform/botstopper/how-to-use-botstopper.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/hypernode-platform/botstopper/how-to-use-botstopper.md b/docs/hypernode-platform/botstopper/how-to-use-botstopper.md index b7516935..8de60f96 100644 --- a/docs/hypernode-platform/botstopper/how-to-use-botstopper.md +++ b/docs/hypernode-platform/botstopper/how-to-use-botstopper.md @@ -97,6 +97,7 @@ The standard policy does the following: 1. Allows Hypernode platform services, payment providers, monitoring tools, and common e-commerce integrations. 1. Allows IP addresses on the Hypernode WAF allowlist. +1. Allows requests that your Hypernode, or any other node in your cluster, sends to itself, for example an extension that fetches WordPress content from your own domain, or a cache warmer requesting storefront pages. 1. Runs your custom pre-policy from `/data/web/botstopper/pre.policy.yml`. 1. Denies sensitive Magento media paths, such as `/media/customer/`, `/media/import/`, and `/media/downloadable/`. 1. Allows storefront assets, such as `/static/`, normal `/media/` files, etc.