https://lethargy.org/~jesus/writes/a-guide-to-nomenclature-selection/
and other excellent resources.
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@
1878547 13f79535-47bb-0310-9956-
ffa450edef68
<p>This policy will be rejected if the server response contains a
<code>Vary</code> header, and that header in turn contains a header
- blacklisted by the administrator.</p>
+ forbidden by the administrator.</p>
<p>The <code>Vary</code> header is described in full in
<a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.44">
cipher suite will force it to simply refuse and fall back to HTTP 1.1. This is a common mistake
that is done while configuring httpd for HTTP/2 the first time, so please keep it in mind to avoid
long debugging sessions! If you want to be sure about the cipher suite to choose please avoid
- the ones listed in the <a href="http://httpwg.org/specs/rfc7540.html#BadCipherSuites">HTTP/2 TLS blacklist</a>.</p>
+ the ones listed in the <a href="http://httpwg.org/specs/rfc7540.html#BadCipherSuites">HTTP/2 TLS reject list</a>.</p>
</note>
<p>The order of protocols mentioned is also relevant. By default, the first one is the
most preferred protocol. When a client offers multiple choices, the one most to the
<section id="host-deny">
- <title>Denying Hosts in a Blacklist</title>
+ <title>Denying Hosts in a Reject List</title>
<dl>
<dt>Description:</dt>
<dd>
- <p>We wish to maintain a blacklist of hosts, rather like
+ <p>We wish to maintain a list of hosts, rather like
<code>hosts.deny</code>, and have those hosts blocked from
accessing our server.</p>
</dd>