Defining Routes¶

A full route definition can contain up to seven parts:

1. The URL path route. This is matched against the URL passed to the RequestContext, and can contain named wildcard placeholders (e.g. {placeholders}) to match dynamic parts in the URL.
2. An array of default values. This contains an array of arbitrary values that will be returned when the request matches the route.
3. An array of requirements. These define constraints for the values of the placeholders as regular expressions.
4. An array of options. These contain internal settings for the route and are the least commonly needed.
5. A host. This is matched against the host of the request. See How to Match a Route Based on the Host for more details.
6. An array of schemes. These enforce a certain HTTP scheme (http, https).
7. An array of methods. These enforce a certain HTTP request method (HEAD, GET, POST, …).

Take the following route, which combines several of these ideas:

$route = new Route(
    '/archive/{month}', // path
    array('_controller' => 'showArchive'), // default values
    array('month' => '[0-9]{4}-[0-9]{2}', 'subdomain' => 'www|m'), // requirements
    array(), // options
    '{subdomain}.example.com', // host
    array(), // schemes
    array() // methods
);

// ...

$parameters = $matcher->match('/archive/2012-01');
// array(
//     '_controller' => 'showArchive',
//     'month' => '2012-01',
//     'subdomain' => 'www',
//     '_route' => ...
//  )

$parameters = $matcher->match('/archive/foo');
// throws ResourceNotFoundException

In this case, the route is matched by /archive/2012-01, because the {month} wildcard matches the regular expression wildcard given. However, /archive/foo does not match, because “foo” fails the month wildcard.

When using wildcards, these are returned in the array result when calling match. The part of the path that the wildcard matched (e.g. 2012-01) is used as value.

$route = new Route(
    '/start/{suffix}',
    array('suffix' => ''),
    array('suffix' => '.*')
);

Using Prefixes¶

You can add routes or other instances of Symfony\Component\Routing\RouteCollection to another collection. This way you can build a tree of routes. Additionally you can define a prefix and default values for the parameters, requirements, options, schemes and the host to all routes of a subtree using methods provided by the RouteCollection class:

$rootCollection = new RouteCollection();

$subCollection = new RouteCollection();
$subCollection->add(...);
$subCollection->add(...);
$subCollection->addPrefix('/prefix');
$subCollection->addDefaults(array(...));
$subCollection->addRequirements(array(...));
$subCollection->addOptions(array(...));
$subCollection->setHost('admin.example.com');
$subCollection->setMethods(array('POST'));
$subCollection->setSchemes(array('https'));

$rootCollection->addCollection($subCollection);

Set the Request Parameters¶

The Symfony\Component\Routing\RequestContext provides information about the current request. You can define all parameters of an HTTP request with this class via its constructor:

public function __construct(
    $baseUrl = '',
    $method = 'GET',
    $host = 'localhost',
    $scheme = 'http',
    $httpPort = 80,
    $httpsPort = 443,
    $path = '/',
    $queryString = ''
)

Normally you can pass the values from the $_SERVER variable to populate the Symfony\Component\Routing\RequestContext. But if you use the HttpFoundation component, you can use its Symfony\Component\HttpFoundation\Request class to feed the Symfony\Component\Routing\RequestContext in a shortcut:

use Symfony\Component\HttpFoundation\Request;

$context = new RequestContext();
$context->fromRequest(Request::createFromGlobals());

Generate a URL¶

While the Symfony\Component\Routing\Matcher\UrlMatcher tries to find a route that fits the given request you can also build a URL from a certain route:

use Symfony\Component\Routing\Generator\UrlGenerator;
use Symfony\Component\Routing\RequestContext;
use Symfony\Component\Routing\Route;
use Symfony\Component\Routing\RouteCollection;

$routes = new RouteCollection();
$routes->add('show_post', new Route('/show/{slug}'));

$context = new RequestContext('/');

$generator = new UrlGenerator($routes, $context);

$url = $generator->generate('show_post', array(
    'slug' => 'my-blog-post',
));
// /show/my-blog-post

Load Routes from a File¶

You’ve already seen how you can easily add routes to a collection right inside PHP. But you can also load routes from a number of different files.

The Routing component comes with a number of loader classes, each giving you the ability to load a collection of route definitions from an external file of some format. Each loader expects a Symfony\Component\Config\FileLocator instance as the constructor argument. You can use the Symfony\Component\Config\FileLocator to define an array of paths in which the loader will look for the requested files. If the file is found, the loader returns a Symfony\Component\Routing\RouteCollection.

If you’re using the YamlFileLoader, then route definitions look like this:

1
2
3
4
5
6
7
8

# routes.yml
route1:
    path:     /foo
    defaults: { _controller: 'MyController::fooAction' }

route2:
    path:     /foo/bar
    defaults: { _controller: 'MyController::foobarAction' }

To load this file, you can use the following code. This assumes that your routes.yml file is in the same directory as the below code:

use Symfony\Component\Config\FileLocator;
use Symfony\Component\Routing\Loader\YamlFileLoader;

// look inside *this* directory
$locator = new FileLocator(array(__DIR__));
$loader = new YamlFileLoader($locator);
$collection = $loader->load('routes.yml');

Besides Symfony\Component\Routing\Loader\YamlFileLoader there are two other loaders that work the same way:

• Symfony\Component\Routing\Loader\XmlFileLoader
• Symfony\Component\Routing\Loader\PhpFileLoader

If you use the Symfony\Component\Routing\Loader\PhpFileLoader you have to provide the name of a PHP file which returns a Symfony\Component\Routing\RouteCollection:

// RouteProvider.php
use Symfony\Component\Routing\RouteCollection;
use Symfony\Component\Routing\Route;

$collection = new RouteCollection();
$collection->add(
    'route_name',
    new Route('/foo', array('_controller' => 'ExampleController'))
);
// ...

return $collection;

use Symfony\Component\Routing\Loader\ClosureLoader;

$closure = function () {
    return new RouteCollection();
};

$loader = new ClosureLoader();
$collection = $loader->load($closure);

The all-in-one Router¶

The Symfony\Component\Routing\Router class is an all-in-one package to quickly use the Routing component. The constructor expects a loader instance, a path to the main route definition and some other settings:

public function __construct(
    LoaderInterface $loader,
    $resource,
    array $options = array(),
    RequestContext $context = null,
    LoggerInterface $logger = null
);

With the cache_dir option you can enable route caching (if you provide a path) or disable caching (if it’s set to null). The caching is done automatically in the background if you want to use it. A basic example of the Symfony\Component\Routing\Router class would look like:

$locator = new FileLocator(array(__DIR__));
$requestContext = new RequestContext('/');

$router = new Router(
    new YamlFileLoader($locator),
    'routes.yml',
    array('cache_dir' => __DIR__.'/cache'),
    $requestContext
);
$router->match('/foo/bar');

Unicode Routing Support¶

The Routing component supports UTF-8 characters in route paths and requirements. Thanks to the utf8 route option, you can make Symfony match and generate routes with UTF-8 characters:

In this route, the utf8 option set to true makes Symfony consider the . requirement to match any UTF-8 characters instead of just a single byte character. This means that so the following URLs would match: /category/日本語, /category/فارسی, /category/한국어, etc. In case you are wondering, this option also allows to include and match emojis in URLs.

You can also include UTF-8 strings as routing requirements: