mirrors/haproxy
1
0
Fork 0
mirror of https://git.haproxy.org/git/haproxy.git/ synced 2025-09-21 13:51:26 +02:00
Code Issues Projects Releases Wiki Activity

DOC: Add more info about request formatting in http-check send description

Browse Source 
Only one Host header can be defined and some headers are automatically skipped
(Connection, Content-Length and Transfer-Encoding). In addition, a note about
the synchronisation of the Host header value and the request uri has been added.
This commit is contained in:
Christopher Faulet 2020-04-29 14:20:47 +02:00
parent a5c14ef767
commit 9df910c7f3
1 changed files with 15 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
doc/configuration.txt
View File

@ -4681,15 +4681,27 @@ http-check send [meth <method>] [uri <uri>] [ver <version>] [comment <msg>]
In addition to the request line defined by the "option httpchk" directive,
this one is the valid way to add some headers and optionally a body to the
request sent during HTTP health checks. If a body is defined, the associate
"Content-Length" header is automatically added. The old trick consisting to
add headers after the version string on the "option httpchk" line is now
"Content-Length" header is automatically added. Thus, this header or
"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" direcive is defined independently of this directive, just
like the state header if the directive "http-check send-state" is defined.
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".
header should not be present in the request provided by "http-check send". If
so, it will be ignored.
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
Host is inserted in the request, the request authority is accordingly
updated. Thus, don't be surprised if the Host header value overwrites the
configured request authority.
Note also for now, no Host header is automatically added in HTTP/1.1 or above
requests. You should add it explicitly.
See also : "option httpchk", "http-check send-state" and "http-check expect".