Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit 1bf9b47

Browse filesBrowse files
committed
Some minor rewords
1 parent 903ddbe commit 1bf9b47
Copy full SHA for 1bf9b47

File tree

Expand file treeCollapse file tree

4 files changed

+5
-5
lines changed
Filter options
Expand file treeCollapse file tree

4 files changed

+5
-5
lines changed

‎frontend/encore/babel.rst

Copy file name to clipboardExpand all lines: frontend/encore/babel.rst
+1-1Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ Need to extend the Babel configuration further? The easiest way is via
2424
babelConfig.plugins.push('styled-jsx/babel');
2525
}, {
2626
// node_modules is not processed through Babel by default
27-
// but you can whitelist specific modules to process
27+
// but you can allow some specific modules to be processed
2828
includeNodeModules: ['foundation-sites'],
2929
3030
// or completely control the exclude rule (note that you

‎reference/configuration/framework.rst

Copy file name to clipboardExpand all lines: reference/configuration/framework.rst
+1-1Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -519,7 +519,7 @@ instance), the host might have been manipulated by an attacker.
519519
The Symfony :method:`Request::getHost() <Symfony\\Component\\HttpFoundation\\Request::getHost>`
520520
method might be vulnerable to some of these attacks because it depends on
521521
the configuration of your web server. One simple solution to avoid these
522-
attacks is to whitelist the hosts that your Symfony application can respond
522+
attacks is to configure a list of hosts that your Symfony application can respond
523523
to. That's the purpose of this ``trusted_hosts`` option. If the incoming
524524
request's hostname doesn't match one of the regular expressions in this list,
525525
the application won't respond and the user will receive a 400 response.

‎reference/constraints/Uuid.rst

Copy file name to clipboardExpand all lines: reference/constraints/Uuid.rst
+1-1Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ UUID
44
Validates that a value is a valid `Universally unique identifier (UUID)`_ per `RFC 4122`_.
55
By default, this will validate the format according to the RFC's guidelines, but this can
66
be relaxed to accept non-standard UUIDs that other systems (like PostgreSQL) accept.
7-
UUID versions can also be restricted using a whitelist.
7+
UUID versions can also be restricted using a list of allowed versions.
88

99
========== ===================================================================
1010
Applies to :ref:`property or method <validation-property-target>`

‎security.rst

Copy file name to clipboardExpand all lines: security.rst
+2-2Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -759,8 +759,8 @@ like this:
759759
will have ``IS_AUTHENTICATED_REMEMBERED`` but will not have ``IS_AUTHENTICATED_FULLY``.
760760

761761
* ``IS_AUTHENTICATED_ANONYMOUSLY``: *All* users (even anonymous ones) have
762-
this - this is useful when *whitelisting* URLs to guarantee access - some
763-
details are in :doc:`/security/access_control`.
762+
this - this is useful when defining a list of URLs with no access restriction
763+
- some details are in :doc:`/security/access_control`.
764764

765765
.. _retrieving-the-user-object:
766766

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.