{"id":15804,"date":"2018-05-15T15:36:44","date_gmt":"2018-05-15T13:36:44","guid":{"rendered":"https:\/\/belvg.com\/blog\/?p=15804"},"modified":"2019-03-15T12:22:53","modified_gmt":"2019-03-15T10:22:53","slug":"request-routing-flow-in-magento-2","status":"publish","type":"post","link":"https:\/\/belvg.com\/blog\/request-routing-flow-in-magento-2.html","title":{"rendered":"Request Routing Flow in Magento 2"},"content":{"rendered":"

Today we are going to talk about request routing and take a look at its customization process. Additionally, we will show you when it is necessary to create new routers and to customize the existing ones. Let’s get these things under the way.<\/span><\/p>\n

<\/p>\n

What is request routing flow in Magento 2?<\/span><\/strong><\/h2>\n

Routing in Magento is a process, that matches a request received in Magento, and the call of the corresponding control module. First of all, an application is created in the index.php<\/strong> file. Here starts the process of determining which of the routers will be called. Below you can see the parts of the code that are called.<\/span><\/p>\n

$app = $bootstrap->createApplication('Magento\\Framework\\App\\Http');\r\n$bootstrap->run($app);\r\nДалее у созданного application вызывается метод launch()\r\n\/*** Magento\\Framework\\App\\Bootstrap ***\/\r\npublic function run(AppInterface $application)\r\n{\r\n          \/* …. *\/\r\n          $response = $application->launch();\r\n          $response->sendResponse();\r\n          \/* …. *\/\r\n}\r\nThe “dispatch” method is also called here. It returns the result of the request.\r\n\/*** Magento\\Framework\\App\\Http ***\/\r\npublic function launch()\r\n{\r\n \/*** … ***\/\r\n  \/** @var \\Magento\\Framework\\App\\FrontControllerInterface $frontController *\/\r\n  $frontController = $this->_objectManager->get('Magento\\Framework\\App\\FrontControllerInterface');\r\n  $result = $frontController->dispatch($this->_request);\r\n\/*** … ***\/\r\n  return $this->_response;\r\n}<\/pre>\n
If you look at what the “dispatch” method contains, it becomes clear how the request is processed and the router is selected. Let us take a look at this code.<\/span><\/p>\n
Here each of the routers ($this ➔ <\/span>_routerList) is checked for compliance with the query. If found, the \\”Magento\\Framework\\App\\Action”<\/strong> object will be returned.<\/span><\/p>\n
If none of the routers finds a matching query, the standard noroute<\/em> action class is called.<\/span><\/p>\n
l\r\n\/**\r\n* Class FrontController\r\n* @package Magento\\Framework\\App\r\n*\/\r\npublic function dispatch(RequestInterface $request)\r\n  {\r\n\/******* .... *********\/\r\n          \/** @var \\Magento\\Framework\\App\\RouterInterface $router *\/\r\n          foreach ($this->_routerList as $router) {\r\n              try {\r\n                  $actionInstance = $router->match($request);\r\n                  if ($actionInstance) {\r\n                      $request->setDispatched(true);\r\n                      $this->response->setNoCacheHeaders();\r\n                      if ($actionInstance instanceof \\Magento\\Framework\\App\\Action\\AbstractAction) {\r\n                          $result = $actionInstance->dispatch($request);\r\n                      } else {\r\n                          $result = $actionInstance->execute();\r\n                      }\r\n                      break;\r\n                  }\r\n        \/****** … ******\/\r\n      return $result;\r\n  }\r\n}<\/pre>\n
It is easy to notice that the list of routers ($this ➔<\/span> _routerList) is processed in the cycle. By default this list consists of standard routers implementing RouterInterface, which are called in the following sequence:<\/span><\/p>\n
    \n
  1. Base Router<\/span><\/li>\n
  2. CMS Router<\/span><\/li>\n
  3. UrlRewrite Router<\/span><\/li>\n
  4. Default Router<\/span><\/li>\n<\/ol>\n
    Customize request routing<\/b><\/span><\/h2>\n
    Magento allows you to add your router to this list. Now let’s consider an example of creating a custom router.<\/span><\/p>\n
    The registration of a new router takes place in di.xml<\/strong>. Here you can define the class that is responsible for processing the request (item name = “class”), the priority of calling the router (item name = “sortOrder”)<\/span><\/p>\n
    <?xml version=\"1.0\"?>\r\n<config xmlns:xsi=\"http:\/\/www.w3.org\/2001\/XMLSchema-instance\" xsi:noNamespaceSchemaLocation=\"urn:magento:framework:ObjectManager\/etc\/config.xsd\">\r\n  <type name=\"Magento\\Framework\\App\\RouterList\">\r\n      <arguments>\r\n          <argument name=\"routerList\" xsi:type=\"array\">\r\n              <item name=\"newreqrouter\" xsi:type=\"array\">\r\n                  <item name=\"class\" xsi:type=\"string\">BelVG\\NewRequestRouter\\Controller\\Router<\/item>\r\n                  <item name=\"disable\" xsi:type=\"boolean\">false<\/item>\r\n                  <item name=\"sortOrder\" xsi:type=\"string\">30<\/item>\r\n              <\/item>\r\n          <\/argument>\r\n      <\/arguments>\r\n  <\/type>\r\n<\/config><\/pre>\n
    The request will be processed directly in the Router class.<\/span><\/p>\n
    \/* BelVG\\NewRequestRouter\\Controller\\Router*\/\r\nnamespace BelVG\\NewRequestRouter\\Controller;\r\n\/**\r\n* Class Router\r\n* @package BelVG\\NewRequestRouter\\Controller\r\n*\/\r\nclass Router implements \\Magento\\Framework\\App\\RouterInterface\r\n{\r\n \/**\r\n  * @var \\Magento\\Framework\\App\\ActionFactory\r\n  *\/\r\n protected $actionFactory;\r\n \/**\r\n  * Response\r\n  *\r\n  * @var \\Magento\\Framework\\App\\ResponseInterface\r\n  *\/\r\n protected $_response;\r\n \/**\r\n  * @param \\Magento\\Framework\\App\\ActionFactory $actionFactory\r\n  * @param \\Magento\\Framework\\App\\ResponseInterface $response\r\n  *\/\r\n public function __construct(\r\n    \\Magento\\Framework\\App\\ActionFactory $actionFactory,\r\n    \\Magento\\Framework\\App\\ResponseInterface $response\r\n ) {\r\n    $this->actionFactory = $actionFactory;\r\n    $this->_response = $response;\r\n }\r\n \/**\r\n  * Validate and Match\r\n  *\r\n  * @param \\Magento\\Framework\\App\\RequestInterface $request\r\n  * @return bool\r\n  *\/\r\n public function match(\\Magento\\Framework\\App\\RequestInterface $request)\r\n {\r\n    $identifier = trim($request->getPathInfo(), '\/');\r\n    if(strpos($identifier, 'anytestrequest') !== false) {\r\n       $request->setModuleName('newrequest')->setControllerName('test')\r\n          ->setActionName('index');\r\n    } else {\r\n       return;\r\n    }\r\n    return $this->actionFactory->create(\r\n       'Magento\\Framework\\App\\Action\\Forward',\r\n       ['request' => $request]\r\n    );\r\n }\r\n}<\/pre>\n
    You can check out the full version of the example of adding a new router here<\/a>.<\/span><\/p>\n
    When it is necessary to create new routers and to customize the existing ones<\/b><\/span><\/h2>\n
    Sometimes you may need to create your own router or customize an existing one. One good example is the “blog” module<\/span>, when you need to redirect seo<\/span>-friendly URLs to the corresponding posts. For this purpose, the module creates its own Router, which distributes the queries.<\/span><\/p>\n
    Also, when migrating from any other platform to Magento, you may need to retain the connection between the old URLs and the new addresses. To do this, you can also use an additional router, which will contain the logic of finding a matching URL (old_webshop_url – magento_webshop).<\/span><\/p>\n
    Customization of an existing router is required, when there is no way to bypass the processing of a standard router request. For example, the router is run in the queue earlier than the custom one and doesn’t find the path required for customization.<\/span><\/p>\n
    Check out a related article<\/a> to find out more about request routing in Magento 2.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"Describing request routing and flow in Magento 2","protected":false},"author":42,"featured_media":15827,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"image","meta":{"_acf_changed":false,"footnotes":""},"categories":[14,471],"tags":[],"class_list":["post-15804","post","type-post","status-publish","format-image","has-post-thumbnail","hentry","category-magento","category-magento-developer","post_format-post-format-image"],"acf":[],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t