tighten up the rather loose Netscape protocol rules a little bit (at the cost of
blocking some benign cookies).
-A domain denylist and allowlist is provided (both off by default). Only domains
-not in the denylist and present in the allowlist (if the allowlist is active)
+A domain blocklist and allowlist is provided (both off by default). Only domains
+not in the blocklist and present in the allowlist (if the allowlist is active)
participate in cookie setting and returning. Use the *blocked_domains*
constructor argument, and :meth:`blocked_domains` and
:meth:`set_blocked_domains` methods (and the corresponding argument and methods
setting it to :const:`None`.
Domains in block or allow lists that do not start with a dot must equal the
-cookie domain to be matched. For example, ``"example.com"`` matches a denylist
+cookie domain to be matched. For example, ``"example.com"`` matches a blocklist
entry of ``"example.com"``, but ``"www.example.com"`` does not. Domains that do
start with a dot are matched by more specific domains too. For example, both
``"www.example.com"`` and ``"www.coyote.example.com"`` match ``".example.com"``
.. method:: DefaultCookiePolicy.is_blocked(domain)
- Return whether *domain* is on the denylist for setting or receiving cookies.
+ Return whether *domain* is on the blocklist for setting or receiving cookies.
.. method:: DefaultCookiePolicy.allowed_domains()