You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Support for access control rule definition based on a RequestMatcher was introduced in Symfony 6.1.
147
+
132
148
For each incoming request, Symfony will decide which ``access_control``
133
149
to use based on the URI, the client's IP address, the incoming host name,
134
150
and the request method. Remember, the first rule that matches is used, and
@@ -165,54 +181,6 @@ if ``ip``, ``port``, ``host`` or ``method`` are not specified for an entry, that
165
181
Matching the URI is done without ``$_GET`` parameters.
166
182
:ref:`Deny access in PHP code <security-securing-controller>` if you want
167
183
to disallow access based on ``$_GET`` parameter values.
168
-
169
-
.. versionadded:: 6.1
170
-
171
-
From verison 6.1 and up, if you have a custom request matcher, you can use the ``request_matcher`` option to specify the service reference to an access control item. Symfony will use this service as the request matcher for this item and won't take into account other matching options.
0 commit comments