routes.php 2.7 KB

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