summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorThomas Haller <thaller@redhat.com>2019-01-14 18:58:45 +0100
committerThomas Haller <thaller@redhat.com>2019-01-28 17:10:18 +0100
commitb2ce9efebb154542ef1abd020d0d57a787117094 (patch)
treee87368ae5a67a65e95c84824735a08339e0bf9c7
parent96bb5906395f98ec1d71b9644ab1ca0339252b4d (diff)
downloadNetworkManager-th/connectivity-empty-response.tar.gz
man: better explain "connectivity.response" in "NetworkManager.conf" manualth/connectivity-empty-response
-rw-r--r--man/NetworkManager.conf.xml13
1 files changed, 8 insertions, 5 deletions
diff --git a/man/NetworkManager.conf.xml b/man/NetworkManager.conf.xml
index e97b6bb9eb..9b4ed858f3 100644
--- a/man/NetworkManager.conf.xml
+++ b/man/NetworkManager.conf.xml
@@ -1084,12 +1084,15 @@ managed=1
</varlistentry>
<varlistentry>
<term><varname>response</varname></term>
- <listitem><para>If set controls what body content
+ <listitem><para>If set, controls what body content
NetworkManager checks for when requesting the URI for
- connectivity checking. If missing, defaults to
- "NetworkManager is online". If set to empty, the
- HTTP server is expected to answer with status code
- 204 or no data.</para></listitem>
+ connectivity checking. Note that this only compares
+ that the HTTP response starts with the specifid text,
+ it does not compare the exact string. This behavior
+ might change in the future, so avoid relying on it.
+ If missing, the response defaults to "NetworkManager is online".
+ If set to empty, the HTTP server is expected to answer with
+ status code 204 or send no data.</para></listitem>
</varlistentry>
</variablelist>
</para>