From: Rich Bowen This policy will be rejected if the server response contains a
Vary header, and that header in turn contains a header
- blacklisted by the administrator.
The Vary header is described in full in
diff --git a/docs/manual/howto/http2.xml b/docs/manual/howto/http2.xml
index 3f4b63c7f36..1e39b783a16 100644
--- a/docs/manual/howto/http2.xml
+++ b/docs/manual/howto/http2.xml
@@ -129,7 +129,7 @@ Protocols http/1.1
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 HTTP/2 TLS blacklist.
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
diff --git a/docs/manual/rewrite/access.xml b/docs/manual/rewrite/access.xml
index 647f20c81dc..e214ea7a4e3 100644
--- a/docs/manual/rewrite/access.xml
+++ b/docs/manual/rewrite/access.xml
@@ -206,13 +206,13 @@ SetEnvIfNoCase User-Agent ^NameOfBadRobot goaway
We wish to maintain a blacklist of hosts, rather like
+ We wish to maintain a list of hosts, rather like
hosts.deny, and have those hosts blocked from
accessing our server.