mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-09-24 07:11:20 +02:00
DOC: cleanup indentation, alignment, columns and chapters
This patch is a group commit simplify the parsing of the documenation : - remove remaining tabulations - realign some lines - break lines at 80 columns - add missing chapters in the summary - fix chapter numbering format
This commit is contained in:
parent
9b061e3320
commit
dc4d903640
@ -47,6 +47,7 @@ Summary
|
|||||||
3.2. Performance tuning
|
3.2. Performance tuning
|
||||||
3.3. Debugging
|
3.3. Debugging
|
||||||
3.4. Userlists
|
3.4. Userlists
|
||||||
|
3.5. Peers
|
||||||
|
|
||||||
4. Proxies
|
4. Proxies
|
||||||
4.1. Proxy keywords matrix
|
4.1. Proxy keywords matrix
|
||||||
@ -859,7 +860,7 @@ user <username> [password|insecure-password <password>]
|
|||||||
|
|
||||||
|
|
||||||
3.5. Peers
|
3.5. Peers
|
||||||
--------------
|
----------
|
||||||
It is possible to synchronize server entries in stick tables between several
|
It is possible to synchronize server entries in stick tables between several
|
||||||
haproxy instances over TCP connections in a multi-master fashion. Each instance
|
haproxy instances over TCP connections in a multi-master fashion. Each instance
|
||||||
pushes its local updates and insertions to remote peers. Server IDs are used to
|
pushes its local updates and insertions to remote peers. Server IDs are used to
|
||||||
@ -892,7 +893,7 @@ peer <peername> <ip>:<port>
|
|||||||
peer name. This makes it easier to maintain coherent configuration files
|
peer name. This makes it easier to maintain coherent configuration files
|
||||||
across all peers.
|
across all peers.
|
||||||
|
|
||||||
Example:
|
Example:
|
||||||
peers mypeers
|
peers mypeers
|
||||||
peer haproxy1 192.168.0.1:1024
|
peer haproxy1 192.168.0.1:1024
|
||||||
peer haproxy2 192.168.0.2:1024
|
peer haproxy2 192.168.0.2:1024
|
||||||
@ -1372,11 +1373,11 @@ balance url_param <param> [check_post [<max_wait>]]
|
|||||||
that changing a server's weight on the fly will have no
|
that changing a server's weight on the fly will have no
|
||||||
effect, but this can be changed using "hash-type".
|
effect, but this can be changed using "hash-type".
|
||||||
|
|
||||||
hdr(<name>) The HTTP header <name> will be looked up in each HTTP request.
|
hdr(<name>) The HTTP header <name> will be looked up in each HTTP
|
||||||
Just as with the equivalent ACL 'hdr()' function, the header
|
request. Just as with the equivalent ACL 'hdr()' function,
|
||||||
name in parenthesis is not case sensitive. If the header is
|
the header name in parenthesis is not case sensitive. If the
|
||||||
absent or if it does not contain any value, the roundrobin
|
header is absent or if it does not contain any value, the
|
||||||
algorithm is applied instead.
|
roundrobin algorithm is applied instead.
|
||||||
|
|
||||||
An optional 'use_domain_only' parameter is available, for
|
An optional 'use_domain_only' parameter is available, for
|
||||||
reducing the hash algorithm to the main domain part with some
|
reducing the hash algorithm to the main domain part with some
|
||||||
@ -8294,8 +8295,8 @@ The list of currently supported pattern fetch functions is the following :
|
|||||||
url_param(<name>)
|
url_param(<name>)
|
||||||
This extracts the first occurrence of the parameter <name> in
|
This extracts the first occurrence of the parameter <name> in
|
||||||
the query string of the request and uses the corresponding value
|
the query string of the request and uses the corresponding value
|
||||||
to match. A typical use is to get sticky session through url (e.g.
|
to match. A typical use is to get sticky session through url
|
||||||
http://example.com/foo?JESSIONID=some_id with
|
(e.g. http://example.com/foo?JESSIONID=some_id with
|
||||||
url_param(JSESSIONID)), for cases where cookies cannot be used.
|
url_param(JSESSIONID)), for cases where cookies cannot be used.
|
||||||
|
|
||||||
rdp_cookie(<name>)
|
rdp_cookie(<name>)
|
||||||
@ -8917,8 +8918,8 @@ Detailed fields description :
|
|||||||
is the reason why this field must always remain the last one.
|
is the reason why this field must always remain the last one.
|
||||||
|
|
||||||
|
|
||||||
8.2.4 Custom log format
|
8.2.4. Custom log format
|
||||||
-----------------------
|
------------------------
|
||||||
|
|
||||||
The directive log-format allows you to custom the logs in http mode and tcp
|
The directive log-format allows you to custom the logs in http mode and tcp
|
||||||
mode. It takes a string as argument.
|
mode. It takes a string as argument.
|
||||||
|
Loading…
x
Reference in New Issue
Block a user