MINOR: check: do not ignore a connection header for http-check send
Allow the user to specify a custom Connection header for http-check
send. This is useful for example to implement a websocket upgrade check.
If no connection header has been set, a 'Connection: close' header is
automatically appended to allow the server to close the connection
immediately after the request/response.
Update the documentation related to http-check send.
This fixes the github issue #1009.
(cherry picked from commit 6d975f0af650e51c5c8e584d9b6beb413deb6868)
Signed-off-by: Willy Tarreau <w@1wt.eu>
diff --git a/doc/configuration.txt b/doc/configuration.txt
index 39c12c0..b1cf92b 100644
--- a/doc/configuration.txt
+++ b/doc/configuration.txt
@@ -5378,14 +5378,11 @@
"Transfer-encoding" header should not be present in the request provided by
"http-check send". If so, it will be ignored. The old trick consisting to add
headers after the version string on the "option httpchk" line is now
- deprecated. Note also the "Connection: close" header is still added if a
- "http-check expect" directive is defined independently of this directive, just
- like the state header if the directive "http-check send-state" is defined.
+ deprecated.
Also "http-check send" doesn't support HTTP keep-alive. Keep in mind that it
- will automatically append a "Connection: close" header, meaning that this
- header should not be present in the request provided by "http-check send". If
- so, it will be ignored.
+ will automatically append a "Connection: close" header, unless a Connection
+ header has already already been configured via a hdr entry.
Note that the Host header and the request authority, when both defined, are
automatically synchronized. It means when the HTTP request is sent, when a