Proxy Rules

Understanding Rules

Rules allow you to manage how Qpoint will interpret the traffic passing through each proxy endpoint, and act as triggers for mitigating any issues that are identified. These rules are executed during the "Detect & Mitigate" phase of your Proxy Stack. There are 5 default rules created, which can be toggled, reordered, or modified at your discretion:

• Debug

• App Error

• Infrastructure Outage

• Not Found

• Slow Response

Proxy Rules can be found under the "Rules" section of a Vendor Configuration

Managing Rules

Filters

• Content Types

  • Specify the types of content the rule should apply to, such as Application, CSS, JavaScript, Fonts, Images, and Media.

• Match URLs

  • Define the specific paths or URL patterns the rule should apply to.

  • This ensures the rule only triggers for relevant requests.

• Ignore URLs

  • Specify paths or URL patterns that the rule should not apply to.

  • Useful for excluding certain requests from being processed by the rule.

• Match Tags

  • Tags extracted from the request that can be used to further filter when the rule should be applied.

Triggers

• HTTP Response Status Codes

  • Specify the HTTP status codes that should trigger this rule, e.g., 2xx for successful responses, 4xx for client errors, and 5xx for server errors.

• Slow Request Duration

  • Define a threshold for request duration, beyond which the rule will be triggered.

• Content Found In Body

  • Specify particular content or patterns in the body that should trigger the rule.

• Empty Body

  • Rule is triggered if the response body is empty.

Actions

• Retries

  • Define the number of times a request should be retried.

• Report as Issue

  • If selected, report the occurrence as an issue for further investigation in the debug and overview dashboards.

• Record Request Headers

  • Log the headers of the request for debugging or auditing purposes.

• Record Request Body

  • Log the body of the request for debugging or auditing purposes.

• Record Response Headers

  • Log the headers of the response for debugging or auditing purposes.

• Record Response Body

  • Log the body of the response for debugging or auditing purposes.

• Take Screenshot

  • Capture a screenshot at the time the rule is triggered. Useful for debugging and visual verification.