The may_terminate
option will indicate to the router that 'this' route is able to be matched solely on the value of its route
; even when it defines child_routes
.
Consider the following example route configuration.
'router' => [
'routes' => [
'home' => [
'type' => 'literal',
'options' => [
'route' => '/home',
],
'may_terminate' => false,
'child_routes' => [
'foo' => [
'type' => 'literal',
'options' => [
'route' => '/foo',
],
],
],
],
],
],
There is some ambiguity in the above configuration, which only occurs with routes that define children. Do we want to allow our users to match on two routes or just one?
We could allow matching on just the /home
part; which would mean we have two routes both
/home
and /home/foo
or we might only want to allow /home/foo
.
This is where the may_terminate
option is used. If we browsed to /home
in our browser, when the routing occurs the router cannot regard the home
route as a matchable route as may_terminate = false
. In ZF2 terminology the router cannot "terminate" at this route and continues on searching for a match into the child_routes
, which will fail and a 404 error will be raised.
So by modifying the value of the may_terminate
option in the above example, we can change the routes that can be matched on.
may_terminate = true
may_terminate = false
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…