Block rules let you define which URL paths are off-limits during a testing engagement. When a researcher sends a request matching a block rule, the proxy returns the configured HTTP status code instead of forwarding the request to your origin.Documentation Index
Fetch the complete documentation index at: https://docs.hackgate.io/llms.txt
Use this file to discover all available pages before exploring further.
Block rule structure
Each rule in the block list is a JSON object with the following fields:| Field | Type | Required | Description |
|---|---|---|---|
PathPrefix | string | Yes | URL path prefix to match. Must start with /. |
Methods | array of strings | No | HTTP methods to match. Use ["*"] for all methods. Defaults to ["*"]. |
Status | integer | Yes | HTTP status code to return (100–599). |
Enabled | boolean | Yes | Whether this rule is active. |
View current block rules
Retrieve the current block rules for a site:Update block rules
TheblockListJson field is a JSON-encoded string containing an array of block rule objects. To update the rules, POST the full array:
Common examples
Clear all block rules
To remove all block rules, setblockListJson to an empty array:
PathPrefix must start with /. A PathPrefix of /admin matches /admin, /admin/users, /admin/settings, and any other path beginning with /admin.