O Guia Definitivo do Yii 1.1

The rules are specified as an array of pattern-route pairs, each corresponding to a single
rule. The pattern of a rule is a string used to match the path info part of URLs. And the
route of a rule should refer to a valid controller route.
Besides the above pattern-route format, a rule may also be specified with customized
options, like the following:
'pattern1'=>array('route1', 'urlSuffix'=>'.xml', 'caseSensitive'=>false)
In the above, the array contains a list of customized options. As of version 1.1.0, the
following options are available:
• urlSuffix: the URL suffix used specifically for this rule. Defaults to null, meaning using
the value ofCUrlManager::urlSuffix.
• caseSensitive: whether this rule is case sensitive. Defaults to null, meaning using the
value ofCUrlManager::caseSensitive.
• defaultParams: the default GET parameters (name=>value) that this rule provides.
When this rule is used to parse the incoming request, the values declared in this
property will be injected into $_GET.
• matchValue: whether the GET parameter values should match the corresponding
sub-patterns in the rule when creating a URL. Defaults to null, meaning using the
value of CUrlManager::matchValue. If this property is false, it means a rule will be
used for creating a URL if its route and parameter names match the given ones. If
this property is set true, then the given parameter values must also match the
corresponding parameter sub-patterns. Note that setting this property to true will
degrade performance.
Using Named Parameters
A rule can be associated with a few GET parameters. These GET parameters appear in
the rule's pattern as special tokens in the following format:
<ParamName:ParamPattern>
Where ParamName specifies the name of a GET parameter, and the optional
ParamPattern specifies the regular expression that should be used to match the value of
the GET parameter. In case whenParamPattern is omitted, it means the parameter should
match any characters except the slash /. When creating a URL, these parameter tokens
will be replaced with the corresponding parameter values; when parsing a URL, the
corresponding GET parameters will be populated with the parsed results.
Let's use some examples to explain how URL rules work. We assume that our rule set
consists of three rules: