Warning: You are browsing the documentation for version 2.7 which is not maintained anymore.
If some of your projects are still using this version, consider upgrading.
The Request body listener makes it possible to decode the contents of a request
in order to populate the “request” parameter bag of the Request. This for
example allows to receive data that normally would be sent via POST as
application/x-www-form-urlencoded in a different format (for example
application/json) in a PUT.
You can add a decoder for a custom format. You can also replace the default
decoder services provided by the bundle for the
Below you can see how to override the decoder for the json format (the xml
decoder is explicitly kept to its default service):
1 2 3 4 5
fos_rest: body_listener: decoders: json: acme.decoder.json xml: fos_rest.decoder.xml
Your custom decoder service must use a class that implements the
If you want to be able to use a checkbox within a form and have true and false
values (without any issue) you have to use:
(available since FosRestBundle 0.8.0)
If the listener receives content that it tries to decode but the decode fails
then a BadRequestHttpException will be thrown with the message:
'Invalid ' .
$format . ' message received'. When combined with the exception controller
support this means your API will provide
useful error messages to your API users if they are making invalid requests.
Array normalizers allow to transform the data after it has been decoded in order to facilitate its processing.
For example, you may want your API’s clients to be able to send requests with
underscored keys but if you use a decoder without a normalizer, you will receive
the data as it is and it can lead to incorrect mapping if you submit the request
directly to a form. If you wish the body listener to transform underscored keys
to camel cased ones, you can use the
camel_keys array normalizer:
1 2 3
fos_rest: body_listener: array_normalizer: fos_rest.normalizer.camel_keys
If you want to ignore leading underscores, for example in
_username you can
instead use the
Sometimes an array contains a key, which once normalized, will override an
existing array key. For example
foo_Bar will both lead to
fooBar. If the normalizer receives this data, the listener will throw a
BadRequestHttpException with the message
The key "foo_Bar" is invalid as it
will override the existing key "fooBar".
If you use the
camel_keys normalizer, you must be careful when choosing
your form name.
You can also create your own array normalizer by implementing the
1 2 3
fos_rest: body_listener: array_normalizer: acme.normalizer.custom
By default, the array normalizer is only applied to requests with a decodable format.
If you want form data to be normalized, you can use the
1 2 3 4 5
fos_rest: body_listener: array_normalizer: service: fos_rest.normalizer.camel_keys forms: true
Using the ArrayNormalizer with login forms¶
If you use the default configuration for the csrf token fieldname (
the Array normalizer will mangle the field name. To make it work, use a name that
is camelcased, like this:
1 2 3 4 5 6 7
security: firewalls: admin: # ... form_login: # ... csrf_parameter: _csrfToken
This work, including the code samples, is licensed under a Creative Commons BY-SA 3.0 license.