1-33

Symfony2 – Franz Jordán 2011
integer. Fortunately, regular expression requirements can easily be added for each parameter.
For example:
blog:
pattern: /blog/{page}
defaults: { _controller: AcmeBlogBundle:Blog:index, page: 1 }
requirements:
page: \d+
The \d+ requirement is a regular expression that says that the value of the {page} parameter
must be a digit (i.e. a number). The blog route will still match on a URL like /blog/2 (because
2 is a number), but it will no longer match a URL like /blog/my-blog-post (because myblog-post
is not a number).
As a result, a URL like /blog/my-blog-post will now properly match the blog_show route.
URL route parameters
/blog/2 blog {page} = 2
/blog/my-blog-post blog_show {slug} = my-blog-post
Earlier Routes always Win
What this all means is that the order of the routes is very important. If theblog_show route
were placed above the blog route, the URL /blog/2 would matchblog_show instead
of blog since the {slug} parameter of blog_show has no requirements. By using proper
ordering and clever requirements, you can accomplish just about anything.
Since the parameter requirements are regular expressions, the complexity and flexibility of each
requirement is entirely up to you. Suppose the homepage of your application is available in two
different languages, based on the URL:
homepage:
pattern: /{culture}
defaults: { _controller: AcmeDemoBundle:Main:homepage, culture: en }
requirements:
culture: en|fr
For incoming requests, the {culture} portion of the URL is matched against the regular
expression(en|fr).
/ {culture} = en
/en {culture} = en
/fr
{culture} = fr
/es won't match this route
60