1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
|
###########
URI Routing
###########
Typically there is a one-to-one relationship between a URL string and
its corresponding controller class/method. The segments in a URI
normally follow this pattern::
example.com/class/function/id/
In some instances, however, you may want to remap this relationship so
that a different class/method can be called instead of the one
corresponding to the URL.
For example, let's say you want your URLs to have this prototype::
example.com/product/1/
example.com/product/2/
example.com/product/3/
example.com/product/4/
Normally the second segment of the URL is reserved for the method
name, but in the example above it instead has a product ID. To
overcome this, CodeIgniter allows you to remap the URI handler.
Setting your own routing rules
==============================
Routing rules are defined in your *application/config/routes.php* file.
In it you'll see an array called ``$route`` that permits you to specify
your own routing criteria. Routes can either be specified using wildcards
or Regular Expressions.
Wildcards
=========
A typical wildcard route might look something like this::
$route['product/:num'] = 'catalog/product_lookup';
In a route, the array key contains the URI to be matched, while the
array value contains the destination it should be re-routed to. In the
above example, if the literal word "product" is found in the first
segment of the URL, and a number is found in the second segment, the
"catalog" class and the "product_lookup" method are instead used.
You can match literal values or you can use two wildcard types:
**(:num)** will match a segment containing only numbers.
**(:any)** will match a segment containing any character (except for '/', which is the segment delimiter).
.. note:: Wildcards are actually aliases for regular expressions, with
**:any** being translated to **[^/]+** and **:num** to **[0-9]+**,
respectively.
.. note:: Routes will run in the order they are defined. Higher routes
will always take precedence over lower ones.
.. note:: Route rules are not filters! Setting a rule of e.g.
'foo/bar/(:num)' will not prevent controller *Foo* and method
*bar* to be called with a non-numeric value if that is a valid
route.
Examples
========
Here are a few routing examples::
$route['journals'] = 'blogs';
A URL containing the word "journals" in the first segment will be
remapped to the "blogs" class.
::
$route['blog/joe'] = 'blogs/users/34';
A URL containing the segments blog/joe will be remapped to the "blogs"
class and the "users" method. The ID will be set to "34".
::
$route['product/(:any)'] = 'catalog/product_lookup';
A URL with "product" as the first segment, and anything in the second
will be remapped to the "catalog" class and the "product_lookup"
method.
::
$route['product/(:num)'] = 'catalog/product_lookup_by_id/$1';
A URL with "product" as the first segment, and a number in the second
will be remapped to the "catalog" class and the
"product_lookup_by_id" method passing in the match as a variable to
the method.
.. important:: Do not use leading/trailing slashes.
Regular Expressions
===================
If you prefer you can use regular expressions to define your routing
rules. Any valid regular expression is allowed, as are back-references.
.. note:: If you use back-references you must use the dollar syntax
rather than the double backslash syntax.
A typical RegEx route might look something like this::
$route['products/([a-z]+)/(\d+)'] = '$1/id_$2';
In the above example, a URI similar to products/shirts/123 would instead
call the "shirts" controller class and the "id_123" method.
With regular expressions, you can also catch a segment containing a
forward slash ('/'), which would usually represent the delimiter between
multiple segments.
For example, if a user accesses a password protected area of your web
application and you wish to be able to redirect them back to the same
page after they log in, you may find this example useful::
$route['login/(.+)'] = 'auth/login/$1';
That will call the "auth" controller class and its ``login()`` method,
passing everything contained in the URI after *login/* as a parameter.
For those of you who don't know regular expressions and want to learn
more about them, `regular-expressions.info <http://www.regular-expressions.info/>`
might be a good starting point.
.. note:: You can also mix and match wildcards with regular expressions.
Callbacks
=========
If you are using PHP >= 5.3 you can use callbacks in place of the normal
routing rules to process the back-references. Example::
$route['products/([a-zA-Z]+)/edit/(\d+)'] = function ($product_type, $id)
{
return 'catalog/product_edit/' . strtolower($product_type) . '/' . $id;
};
Reserved Routes
===============
There are two reserved routes::
$route['default_controller'] = 'welcome';
This route indicates which controller class should be loaded if the URI
contains no data, which will be the case when people load your root URL.
In the above example, the "welcome" class would be loaded. You are
encouraged to always have a default route otherwise a 404 page will
appear by default.
::
$route['404_override'] = '';
This route indicates which controller class should be loaded if the
requested controller is not found. It will override the default 404
error page. It won't affect to the ``show_404()`` function, which will
continue loading the default *error_404.php* file at
*application/errors/error_404.php*.
.. important:: The reserved routes must come before any wildcard or
regular expression routes.
|
