How to Use HTTP Methods beyond GET and POST in Routes
Edit this pageWarning: You are browsing the documentation for Symfony 2.3, which is no longer maintained.
Read the updated version of this page for Symfony 6.3 (the current stable version).
How to Use HTTP Methods beyond GET and POST in Routes
The HTTP method of a request is one of the requirements that can be checked when seeing if it matches a route. This is introduced in the routing chapter of the book "Routing" with examples using GET and POST. You can also use other HTTP verbs in this way. For example, if you have a blog post entry then you could use the same URL path to show it, make changes to it and delete it by matching on GET, PUT and DELETE.
1 2 3 4 5 6 7 8 9 10 11 12 13 14
blog_show:
path: /blog/{slug}
defaults: { _controller: AppBundle:Blog:show }
methods: [GET]
blog_update:
path: /blog/{slug}
defaults: { _controller: AppBundle:Blog:update }
methods: [PUT]
blog_delete:
path: /blog/{slug}
defaults: { _controller: AppBundle:Blog:delete }
methods: [DELETE]Faking the Method with _method
Note
The _method functionality shown here is disabled by default in Symfony 2.2
and enabled by default in Symfony 2.3. To control it in Symfony 2.2, you
must call Request::enableHttpMethodParameterOverride
before you handle the request (e.g. in your front controller). In Symfony
2.3, use the FrameworkBundle Configuration ("framework") option.
Unfortunately, life isn't quite this simple, since most browsers do not support
sending PUT and DELETE requests via the `method` attribute in an HTML form. Fortunately,
Symfony provides you with a simple way of working around this limitation. By including
a _method parameter in the query string or parameters of an HTTP request, Symfony
will use this as the method when matching routes. Forms automatically include a
hidden field for this parameter if their submission method is not GET or POST.
See the related chapter in the forms documentation
for more information.
