Routes are recursively defined in the Zend Framework. This means any route may have a collection of routes that are “child routes”. This is a very important concept for creating complicated web applications, where defining all URL’s might make for a hassle if one root node changes name.
'zf' => array( 'type' => 'Literal', 'options' => array( 'route' => '/zf', 'defaults' => array( '__NAMESPACE__' => 'Application\Controller', 'controller' => 'Article', 'action' => 'index', ), ), 'may_terminate' => true, 'child_routes' => array( 'default' => array( 'type' => 'Segment', 'options' => array( 'route' => '/:action', 'constraints' => array( 'action' => '[a-zA-Z][a-zA-Z0-9_-]*', ), ), ), ), ),
This route is actually from my zulworks website, and it is the one that runs when you request
/zf/routing. Notice how, in this example, you end up with the controller
Application\Controller\Article, with an action of
The Zend Framework application creates and maintains a route stack interface designed to allow you to configure your routes in a flexible and powerful manner. The router in the Zend framework is designed to mimic the routing types and schemas of Ruby on Rails. Let’s look at a basic route:
'home' => array( 'type' => 'Zend\Mvc\Router\Http\Literal', 'options' => array( 'route' => '/email@example.com', 'defaults' => array( 'controller' => 'Application\Controller\Users', // Controller or Controller Alias 'action' => 'view', // Method to be called, viewAction() in this case ), ), ),
This is a literal HTTP route, it matches the resource portion of the HTTP request. You can determine the type of route by setting the ‘type’ flag to be an instance of any class you have a factory set up for. Notice, you can make your own route match classes via this mechanism.
HTTP1/1 GET /firstname.lastname@example.org
A literal HTTP route only matches if the entire request string matches. Literally. This makes them less useful for most routes, however, it can allow you to improve the performance (somewhat negligibly, but still improve) of incredibly common pages that require some amount of recursive route matching to determine the path for. For example, you may use it to cache some URL’s that have get parameters for your biggest companies, short-circuiting the route matching and supplying it directly with a namespace, controller, action, and other URL parameters.
This is exactly like a literal route, only it only matches a portion of the URL string, along with wildcard characters. You would typically use this to only match a portion in the middle of the string, as a simple segment route would usually be a child route to a literal route. The segment route offers basic glob functionality as well, allowing the use of the * character as a wildcard.
'default' => array( 'type' => 'Segment', 'options' => array( 'route' => '/:action', 'constraints' => array( 'action' => '[a-zA-Z][a-zA-Z0-9_-]*', ), ), ),
Optional segments can be defined with the brackets syntax:
'testing' => array( 'type' => 'Segment', 'options' => array( 'route' => '/test/:a[/:b[/:c[/:d[/]]]]', 'defaults' => array( 'controller' => 'Test', 'action' => 'test', ), ), ),
This is a route I used to test route matching. It actually works very well for allowing the input of up to four arguments, as a catch all. You may use this as a parent route for any routes you want to play with, and then see what you can/can't override.
ZF2 is designed to make RESTful web applications, so it’s essential that your framework has the capability to respond to all HTTP methods. This is done via the method route match, which will only match a given segment route if the HTTP verb int he request corresponds to the route config given.
'add' => array ( 'type' => 'Segment', 'options' => array( 'route' => '/add/:item', 'defaults' => array( 'action' => 'add', ), ), 'child_routes' => array( 'put' => array ( 'type' => 'Zend\Mvc\Router\Http\Method', 'options' => array( 'verb' => 'PUT', 'defaults' => array( 'action' => 'put', ), ) ), 'get' => array ( 'type' => 'Zend\Mvc\Router\Http\Method', 'options' => array( 'verb' => 'GET', 'defaults' => array( 'action' => 'add', ), ) ), ), ),
This route will do the action
Controller::putAction() for this HTTP request:
HTTP1/1 PUT /add/12345 foo=true&bar=false
and the action
Controller::addAction() for GET requests, and serve a 404 for all others.
The Zend\Mvc\Router\Http\Part class allows you to define a partial route-match tree. In fact, if you pass into Part::factory that which you supply in your module config files, you will end up with the exact same RouteMatch as you would.
Matches a route segment that contains any characters. I assume this is the least useful route type available.
The scheme and hostname routes allow your application to react to both the hostname used to identify the computer as well as the url scheme provided.
'http' => array( 'type' => 'Zend\Mvc\Router\Http\Scheme', 'options' => array( 'scheme' => 'http', 'priority' => 2, 'defaults' => array( 'controller' => 'Application\Controller\Http', 'action' => 'index', ), ), ),
This route will snag ALL requests using regular HTTP, for the purposes of forwarding the user to HTTPS. The reason that child routes aren't matched first is because of the highlighted "priority" portion of the route definition.
It is important that when you design a URL to reduce redundancy from left to right. Let’s look at how we can do this with an example. Let’s assume we have three resources that provide an interface to the ACL system.
Route Resource Parameters 1 Role company, role 2 Roles company 3 Users company
Route 1 requires two parameters, it is very tempting to put them together (at the end). If we follow suit with all three routes we end up with this set:
/acl/roles/:company/:role[/] => /acl/roles/mpn/developer /acl/roles/:company[/] => /acl/roles/mpn /acl/users/:company[/] => /acl/users/mpn
Except this scheme has a problem, we’re thinking about this in terms of requesting a resource and passing in arguments:
/district.php?company=28&categ=40 => district = (28, 40) /district/28/categ/40 => district = 28, category = 40
Instead of thinking of these things in terms of resources that take arguments (that’s what they are, but that’s not semantically what a url represents), we should look at these in terms of collections.
URL Collection /acl/roles Roles /acl/users Users
Now we’re getting somewhere, but wait, this is still not perfect (although some could argue it is.) Let’s expand this out a little bit
URL Collection /acl/roles/mpn Roles at MPN /acl/users/mpn Users at MPN
Notice the redundancy? For every collection above ACL, we repeat MPN multiple times. Let’s change up our scheme a little bit and see what it means semantically.
/acl/:company/roles/:role[/] => /acl/mpn/roles/developer /acl/:company/roles[/] => /acl/mpn/roles /acl/:company/users[/] => /acl/mpn/users
This looks like equally as good a URL scheme, but there’s one advantage in what it logically represents
URL Collection /acl/mpn ACL Rules at MPN /acl/mpn/roles Roles /acl/mpn/users Users
Aha! Our redundancy is gone, fantastic. So there’s our amazing URL... but what happens if we design them badly and have to change them around logically? That’s no problem! The router can build URL’s based on route prototypes and parameters!
$url = $this->url()->fromRoute('acl/roles', array('company' => 'mpn', 'role' => 'developer'));