Laravel Routes

Hello Developers,

Laravel 5 Implemented routes as sepeately, previously we have in app/Http/routes.php in Laravel 4.

In Laravel 5 maintaining separate directory.

In the newer version, Laravel 5.3, we have a folder named 'routes', where we can find the following files:

• api.php
• console.php
• web.php

For this new version, the routes for your controllers, you can put inside web.php file

Detailed Information:

There is

1. routes/web.php : routes file which works similar to routes.php file where you can have your routes and all the POST routes in web.php file will be validated for the CSRF Token similar to normal Laravel Post route.
2. routes/api.php : routes file where you can have your Application's API routes, the URL will be example.com/api/ Eg. If you have route getUsers then the API URL will be example.com/api/getUsers. The most important thing to notice is POST requests to an API url will not be validated for CSRF Token.
3. routes/console.php : routes file where you can define your Artisan commands which you can run from Laravel Artisan CLI.

Codeigniter Hooks

Hook Points

The following is a list of available hook points.

• pre_system Called very early during system execution. Only the benchmark and hooks class have been loaded at this point. No routing or other processes have happened.
• pre_controller Called immediately prior to any of your controllers being called. All base classes, routing, and security checks have been done.
• post_controller_constructor Called immediately after your controller is instantiated, but prior to any method calls happening.
• post_controller Called immediately after your controller is fully executed.
• display_override Overrides the _display() method, used to send the finalized page to the web browser at the end of system execution. This permits you to use your own display methodology. Note that you will need to reference the CI superobject with $this->CI =& get_instance() and then the finalized data will be available by calling $this->CI->output->get_output().
• cache_override Enables you to call your own method instead of the _display_cache() method in the Output Library. This permits you to use your own cache display mechanism.
• post_system Called after the final rendered page is sent to the browser, at the end of system execution after the finalized data is sent to the browser.