Skip to content

[Security] add tip about using custom functions #9552

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 19, 2018
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions security/access_control.rst
Original file line number Diff line number Diff line change
Expand Up @@ -301,6 +301,15 @@ and functions including ``request``, which is the Symfony
For a list of the other functions and variables, see
:ref:`functions and variables <security-expression-variables>`.

.. tip::

The ``allow_if`` expressions can also contain custom functions registered
with :ref:`expression providers <components-expression-language-provider>`.

.. versionadded:: 4.1
The feature to use custom functions inside ``allow_if`` expressions was
introduced in Symfony 4.1.

Forcing a Channel (http, https)
-------------------------------

Expand Down
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy