In Zend Framework 2, Zend\Mvc\Router\Http\Query is used primarily to allow appending query strings to URLs when assembled. However, due to the fact that it captures any query parameters into the RouteMatch, and the fact that RouteMatch parameters are merged with any parent routes, this can lead to overriding already captured routing parameters, bypassing constraints defined in the parents.
As an example, consider the following route definition:
array(
'user' => array(
'type' => 'segment',
'options' => array(
'route' => '/user/:key',
'defaults' => array(
'controller' => 'UserController',
'action' => 'show-action',
),
'constraints' => array(
'key' => '[a-z0-9]+',
),
),
'child_routes' => array(
'query' => array('type' => 'query'),
),
),
)
If the request URI was /user/foo/?controller=SecretController&key=invalid_value, the RouteMatch returned after routing would contain the following:
array(
'controller' => 'SecretController',
'action' => 'show-action',
'key' => 'invalid_value',
)
This would lead to execution of a different controller than intended, with a value for the key parameter that bypassed the constraints outlined in the parent route.
References
In Zend Framework 2,
Zend\Mvc\Router\Http\Queryis used primarily to allow appending query strings to URLs when assembled. However, due to the fact that it captures any query parameters into the RouteMatch, and the fact that RouteMatch parameters are merged with any parent routes, this can lead to overriding already captured routing parameters, bypassing constraints defined in the parents.As an example, consider the following route definition:
If the request URI was /user/foo/?controller=SecretController&key=invalid_value, the RouteMatch returned after routing would contain the following:
This would lead to execution of a different controller than intended, with a value for the key parameter that bypassed the constraints outlined in the parent route.
References