diff options
Diffstat (limited to 'application/config/routes.php')
| -rw-r--r-- | application/config/routes.php | 46 |
1 files changed, 46 insertions, 0 deletions
diff --git a/application/config/routes.php b/application/config/routes.php new file mode 100644 index 000000000..5f9a58343 --- /dev/null +++ b/application/config/routes.php @@ -0,0 +1,46 @@ +<?php if ( ! defined('BASEPATH')) exit('No direct script access allowed'); +/* +| ------------------------------------------------------------------------- +| URI ROUTING +| ------------------------------------------------------------------------- +| This file lets you re-map URI requests to specific controller functions. +| +| Typically there is a one-to-one relationship between a URL string +| and its corresponding controller class/method. The segments in a +| URL normally follow this pattern: +| +| example.com/class/method/id/ +| +| In some instances, however, you may want to remap this relationship +| so that a different class/function is called than the one +| corresponding to the URL. +| +| Please see the user guide for complete details: +| +| http://codeigniter.com/user_guide/general/routing.html +| +| ------------------------------------------------------------------------- +| RESERVED ROUTES +| ------------------------------------------------------------------------- +| +| There area two reserved routes: +| +| $route['default_controller'] = 'welcome'; +| +| This route indicates which controller class should be loaded if the +| URI contains no data. In the above example, the "welcome" class +| would be loaded. +| +| $route['404_override'] = 'errors/page_missing'; +| +| This route will tell the Router what URI segments to use if those provided +| in the URL cannot be matched to a valid route. +| +*/ + +$route['default_controller'] = "welcome"; +$route['404_override'] = ''; + + +/* End of file routes.php */ +/* Location: ./application/config/routes.php */
\ No newline at end of file |