From 1bf9b473fd9fee3d8980c1a0aefebb4eab8b75dd Mon Sep 17 00:00:00 2001 From: Javier Eguiluz Date: Tue, 13 Jul 2021 12:07:15 +0200 Subject: [PATCH] Some minor rewords --- frontend/encore/babel.rst | 2 +- reference/configuration/framework.rst | 2 +- reference/constraints/Uuid.rst | 2 +- security.rst | 4 ++-- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/frontend/encore/babel.rst b/frontend/encore/babel.rst index 083e45528fc..95ba6086913 100644 --- a/frontend/encore/babel.rst +++ b/frontend/encore/babel.rst @@ -24,7 +24,7 @@ Need to extend the Babel configuration further? The easiest way is via babelConfig.plugins.push('styled-jsx/babel'); }, { // node_modules is not processed through Babel by default - // but you can whitelist specific modules to process + // but you can allow some specific modules to be processed includeNodeModules: ['foundation-sites'], // or completely control the exclude rule (note that you diff --git a/reference/configuration/framework.rst b/reference/configuration/framework.rst index a2f18c2f335..54f65230f3b 100644 --- a/reference/configuration/framework.rst +++ b/reference/configuration/framework.rst @@ -519,7 +519,7 @@ instance), the host might have been manipulated by an attacker. The Symfony :method:`Request::getHost() ` method might be vulnerable to some of these attacks because it depends on the configuration of your web server. One simple solution to avoid these -attacks is to whitelist the hosts that your Symfony application can respond +attacks is to configure a list of hosts that your Symfony application can respond to. That's the purpose of this ``trusted_hosts`` option. If the incoming request's hostname doesn't match one of the regular expressions in this list, the application won't respond and the user will receive a 400 response. diff --git a/reference/constraints/Uuid.rst b/reference/constraints/Uuid.rst index 4406555ac30..9dbde3b3ce5 100644 --- a/reference/constraints/Uuid.rst +++ b/reference/constraints/Uuid.rst @@ -4,7 +4,7 @@ UUID Validates that a value is a valid `Universally unique identifier (UUID)`_ per `RFC 4122`_. By default, this will validate the format according to the RFC's guidelines, but this can be relaxed to accept non-standard UUIDs that other systems (like PostgreSQL) accept. -UUID versions can also be restricted using a whitelist. +UUID versions can also be restricted using a list of allowed versions. ========== =================================================================== Applies to :ref:`property or method ` diff --git a/security.rst b/security.rst index 490ccef1ce9..abc65227c42 100644 --- a/security.rst +++ b/security.rst @@ -759,8 +759,8 @@ like this: will have ``IS_AUTHENTICATED_REMEMBERED`` but will not have ``IS_AUTHENTICATED_FULLY``. * ``IS_AUTHENTICATED_ANONYMOUSLY``: *All* users (even anonymous ones) have - this - this is useful when *whitelisting* URLs to guarantee access - some - details are in :doc:`/security/access_control`. + this - this is useful when defining a list of URLs with no access restriction + - some details are in :doc:`/security/access_control`. .. _retrieving-the-user-object: