routes.php 2.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112
  1. <?php
  2. /*
  3. |--------------------------------------------------------------------------
  4. | Application Routes
  5. |--------------------------------------------------------------------------
  6. |
  7. | Simply tell Laravel the HTTP verbs and URIs it should respond to. It is a
  8. | breeze to setup your applications using Laravel's RESTful routing, and it
  9. | is perfectly suited for building both large applications and simple APIs.
  10. | Enjoy the fresh air and simplicity of the framework.
  11. |
  12. | Let's respond to a simple GET request to http://example.com/hello:
  13. |
  14. | Route::get('hello', function()
  15. | {
  16. | return 'Hello World!';
  17. | });
  18. |
  19. | You can even respond to more than one URI:
  20. |
  21. | Route::post(array('hello', 'world'), function()
  22. | {
  23. | return 'Hello World!';
  24. | });
  25. |
  26. | It's easy to allow URI wildcards using (:num) or (:any):
  27. |
  28. | Route::put('hello/(:any)', function($name)
  29. | {
  30. | return "Welcome, $name.";
  31. | });
  32. |
  33. */
  34. Route::get('/', function()
  35. {
  36. return View::make('home.index');
  37. });
  38. /*
  39. |--------------------------------------------------------------------------
  40. | Application 404 & 500 Error Handlers
  41. |--------------------------------------------------------------------------
  42. |
  43. | To centralize and simplify 404 handling, Laravel uses an awesome event
  44. | system to retrieve the response. Feel free to modify this function to
  45. | your tastes and the needs of your application.
  46. |
  47. | Similarly, we use an event to handle the display of 500 level errors
  48. | within the application. These errors are fired when there is an
  49. | uncaught exception thrown in the application.
  50. |
  51. */
  52. Event::listen('404', function()
  53. {
  54. return Response::error('404');
  55. });
  56. Event::listen('500', function()
  57. {
  58. return Response::error('500');
  59. });
  60. /*
  61. |--------------------------------------------------------------------------
  62. | Route Filters
  63. |--------------------------------------------------------------------------
  64. |
  65. | Filters provide a convenient method for attaching functionality to your
  66. | routes. The built-in "before" and "after" filters are called before and
  67. | after every request to your application, and you may even create other
  68. | filters that can be attached to individual routes.
  69. |
  70. | Let's walk through an example...
  71. |
  72. | First, define a filter:
  73. |
  74. | Route::filter('filter', function()
  75. | {
  76. | return 'Filtered!';
  77. | });
  78. |
  79. | Next, attach the filter to a route:
  80. |
  81. | Router::register('GET /', array('before' => 'filter', function()
  82. | {
  83. | return 'Hello World!';
  84. | }));
  85. |
  86. */
  87. Route::filter('before', function()
  88. {
  89. // Do stuff before every request to your application...
  90. });
  91. Route::filter('after', function($response)
  92. {
  93. // Do stuff after every request to your application...
  94. });
  95. Route::filter('csrf', function()
  96. {
  97. if (Request::forged()) return Response::error('500');
  98. });
  99. Route::filter('auth', function()
  100. {
  101. if (Auth::guest()) return Redirect::to('login');
  102. });