Skip to the content
Documentation

requestrules.ini

No ratings yet

Available since Exponential 6.0.15 (in development, not in a release yet).

Summary

Request rules: what happens to a request before its module view runs.

Description

Request rules: what happens to a request before its module view runs.

Guide with every condition, action and fact, and recipes: doc/eng-us/bc/6.0/view_full_security.md

A rule is a group [Rule-<name>] with conditions and an action. The rules named in RuleList[] are asked in that order about every module view the kernel is about to run -- after the URL alias is translated and after the user's role policies allowed the view. The first rule whose conditions all match decides; when none does, the request runs as it always has.

Rules only ever take access away or send the visitor elsewhere. They never give access that a policy refused.

Do not edit this file. Override it in settings/override/requestrules.ini.append.php every siteaccess settings/siteaccess/<name>/requestrules.ini.append.php one siteaccess extension/<name>/settings/requestrules.ini.append.php

Groups

Group Help
[RequestRuleSettings] Generated example
[Rule-system_url_full_view_to_alias] Generated example
[Rule-system_url_content_view_notfound] Generated example
[Rule-system_url_full_view_audit] Generated example

Location

settings/requestrules.ini; override it in settings/override/requestrules.ini.append.php, in a siteaccess or in an extension.

See also

Help: bc/6.0/view_full_security.md

Generated examples: the settings of requestrules.ini

Added to the reference for Exponential 6.0.15: the 4.x reference had no page for this file. The groups are listed from the file; their settings are described in its comments.

In this section

Contributors

Comments

Add a comment

Comments are read by a moderator before they appear.