mirror of
http://git.haproxy.org/git/haproxy.git/
synced 2025-04-06 17:22:17 +00:00
DOC: assorted typo fixes in the documentation
This is the 8th round of cleanups in various docs
This commit is contained in:
parent
b7faeaddac
commit
4329a9af5a
@ -7722,12 +7722,12 @@ no option logasap
|
|||||||
Using "option logasap", the log message is created as soon as the server
|
Using "option logasap", the log message is created as soon as the server
|
||||||
connection is established in mode tcp, or as soon as the server sends the
|
connection is established in mode tcp, or as soon as the server sends the
|
||||||
complete headers in mode http. Missing information in the logs will be the
|
complete headers in mode http. Missing information in the logs will be the
|
||||||
total number of bytes which will only indicate the amount of data transfered
|
total number of bytes which will only indicate the amount of data transferred
|
||||||
before the message was created and the total time which will not take the
|
before the message was created and the total time which will not take the
|
||||||
remainder of the connection life or transfer time into account. For the case
|
remainder of the connection life or transfer time into account. For the case
|
||||||
of HTTP, it is good practice to capture the Content-Length response header
|
of HTTP, it is good practice to capture the Content-Length response header
|
||||||
so that the logs at least indicate how many bytes are expected to be
|
so that the logs at least indicate how many bytes are expected to be
|
||||||
transfered.
|
transferred.
|
||||||
|
|
||||||
Examples :
|
Examples :
|
||||||
listen http_proxy 0.0.0.0:80
|
listen http_proxy 0.0.0.0:80
|
||||||
@ -12636,7 +12636,7 @@ check
|
|||||||
proxy-protocol header, etc... ). It is possible to change the destination
|
proxy-protocol header, etc... ). It is possible to change the destination
|
||||||
address using "addr" and the port using "port". When done, it is assumed the
|
address using "addr" and the port using "port". When done, it is assumed the
|
||||||
server isn't checked on the service port, and configured encapsulation
|
server isn't checked on the service port, and configured encapsulation
|
||||||
parameters are not reused. One must explicitely set "check-send-proxy" to send
|
parameters are not reused. One must explicitly set "check-send-proxy" to send
|
||||||
connection headers, "check-ssl" to use SSL/TLS.
|
connection headers, "check-ssl" to use SSL/TLS.
|
||||||
|
|
||||||
When "sni" or "alpn" are set on the server line, their value is not used for
|
When "sni" or "alpn" are set on the server line, their value is not used for
|
||||||
|
Loading…
Reference in New Issue
Block a user