Yii Framework Official Guide Series 43 - Special Topic: URL (Creation, Routing, Beautification and Customization)

#Complete URL management of web applications includes two aspects. First, when the user requests the agreed URL, the application needs to parse it into understandable parameters. Second, the application needs to provide a way to create URLs so that the created URLs can be understood by the application. For Yii applications, these are assisted by CUrlManager.

1. Creating URLs

Although URLs can be hard-coded in the controller's view file, they can often be created dynamically with great flexibility:

$url=$this->createUrl($route,$params);

$this refers to the controller instance; $route specifies the requested route requirements; $params lists the requirements attached to the URLGETparameters in .

By default, URLs are created using createUrl in get format. For example, providing $route='post/read' and $params=array('id'=>100) , we will get the following URL:

/index.php?r=post/read&id=100

The parameters are concatenated with a series of Name=Value symbols. Appearing in the request string, the r parameter refers to the requested route. This URL format is not very user-friendly because it requires some non-word characters.

We can make the above URL look cleaner and more self-explanatory by using the so-called 'path format, omitting the query string and adding the GET parameters to the path information as part of the URL:

/index.php/post/read/id/100

To change the URL format, we should configure the urlManager application element so that createUrl can automatically switch to the new format and the application can correctly understand the new URL:

array( ...... 'components'=>array( ...... 'urlManager'=>array( 'urlFormat'=>'path', ), ), );

Please note that we do not need to specify the class of the urlManager element because it is pre-declared as CUrlManager in CWebApplication.

The createurl method generates a relative address. In order to get an absolute URL, we can use the prefix yii">. Tip: This URL is a relative address generated by the createurl method. In order to get an absolute URL, we can use the prefix yii:: app()->hostInfo, or call createAbsoluteUrl

2. User-friendly URLs (user-friendly URLs)

When using path format URL, we can specify certain URL rules make our URLs more user-friendly. For example, we can generate a short URL /post/100 instead of the lengthy /index.php/post/read/id/100 URL creation and parsing through CUrlManager. Specify URL rules.

To specify URL rules, we must set the attributes rules of the urlManager application element:

#

array( ...... 'components'=>array( ...... 'urlManager'=>array( 'urlFormat'=>'path', 'rules'=>array( 'pattern1'=>'route1', 'pattern2'=>'route2', 'pattern3'=>'route3', ), ), ), );

These rules are specified as an array of route format pairs, each pair corresponding to a single rule. The route (route) format must be a valid regular expression without delimiters and modifiers. For the path information part of the matching URL, the route should point to a valid route controller. The

rule can bind a small number of GET parameters that appear in the rule format, with a special token. The format is as follows:

'pattern1'=>array('route1', 'urlSuffix'=>'.xml', 'caseSensitive'=>false)

The above array contains a series of custom option settings, in version 1.1.0 , the following options are valid:

• urlSuffix: The suffix setting rule used by the URL. The default is null, and the setting of CUrlManager::urlSuffix is used.

• caseSensitive: Whether the rule is sensitive to large and small schools, the default is null, and the default value of CUrlManager::caseSensitive is used.

• defaultParams: GET provided by the rule The default value of the parameter (name=>value). When the rule is used to parse the incoming request, the value declared in this attribute will be injected into $_GET.

• matchValue: When created Whether the value of the GET parameter in a URL matches the corresponding sub-pattern in the rule. The default is null, which means that the value in CUrlManager::matchValue is used. If the attribute value is false, it means that if the route and parameter names match The given match then the rule is used to create a URL. If this property is set to true, then the given parameter value must also match the corresponding subpattern parameter value. Note that if the value of this property is set to true Will reduce performance

Use named parameters

A rule can associate some GET parameters. These GET parameters appear as special tokens in the pattern of the rule, as follows:

;

ParamNameindicates the GET parameter name, and the optionalParamPatternindicates what will be used Regular expression matching GET parameter values. When generating a web address (URL), these parameter tokens will be replaced by the corresponding parameter values; when parsing a URL, the corresponding GET parameters will be generated by parsing the results.

We use some examples to explain the URL working rules. Let's assume that our rules include the following three:

##

array( 'posts'=>'post/list', 'post/'=>'post/read', 'post//