From ba70590a9186be101503bc691f5375e5549b1fa2 Mon Sep 17 00:00:00 2001 From: HAProxy Community Date: Tue, 5 Dec 2023 15:52:26 +0000 Subject: [PATCH] Update docs for dev --- docs/dev/configuration.html | 14 ++++---- docs/dev/intro.html | 8 ++--- docs/dev/management.html | 68 ++++++++++++++++++------------------- 3 files changed, 45 insertions(+), 45 deletions(-) diff --git a/docs/dev/configuration.html b/docs/dev/configuration.html index 28ccd8ea..7c3373e2 100644 --- a/docs/dev/configuration.html +++ b/docs/dev/configuration.html @@ -2,7 +2,7 @@ - HAProxy version 2.9-dev12-21 - Configuration Manual + HAProxy version 3.0-dev0 - Configuration Manual @@ -4108,7 +4108,7 @@ You can use left and right arrow keys to navigate between chapters.

- Converted with haproxy-dconv v0.4.2-12 on 2023/12/04 + Converted with haproxy-dconv v0.4.2-12 on 2023/12/05

@@ -4119,9 +4119,9 @@

Configuration Manual

-

version 2.9-dev12-21

+

version 3.0-dev0

- 2023/11/30
+ 2023/12/05

@@ -5392,7 +5392,7 @@

1.1.< the corresponding request in HTTP. For this reason, it is mandatory for the server to reply in the exact same order as the requests were received. In practice, after several attempts by various clients to deploy it, it has been -totally abandonned for its lack of reliability on certain servers. But it is +totally abandoned for its lack of reliability on certain servers. But it is mandatory for servers to support it. The next improvement is the multiplexed mode, as implemented in HTTP/2 and @@ -28957,8 +28957,8 @@

11
- HAProxy 2.9-dev12-21 – Configuration Manual
- , 2023/11/30 + HAProxy 3.0-dev0 – Configuration Manual
+ , 2023/12/05
diff --git a/docs/dev/intro.html b/docs/dev/intro.html index 062d807f..fffc6bc3 100644 --- a/docs/dev/intro.html +++ b/docs/dev/intro.html @@ -2,7 +2,7 @@ - HAProxy version 2.9-dev12-21 - Starter Guide + HAProxy version 3.0-dev0 - Starter Guide @@ -484,7 +484,7 @@ You can use left and right arrow keys to navigate between chapters.

- Converted with haproxy-dconv v0.4.2-12 on 2023/12/04 + Converted with haproxy-dconv v0.4.2-12 on 2023/12/05

@@ -495,7 +495,7 @@

Starter Guide

-

version 2.9-dev12-21

+

version 3.0-dev0


@@ -2515,7 +2515,7 @@

4.4.<
- HAProxy 2.9-dev12-21 – Starter Guide
+ HAProxy 3.0-dev0 – Starter Guide
,

diff --git a/docs/dev/management.html b/docs/dev/management.html index a1c78b46..50b6e439 100644 --- a/docs/dev/management.html +++ b/docs/dev/management.html @@ -2,7 +2,7 @@ - HAProxy version 2.9-dev12-21 - Management Guide + HAProxy version 3.0-dev0 - Management Guide @@ -614,7 +614,7 @@ You can use left and right arrow keys to navigate between chapters.

- Converted with haproxy-dconv v0.4.2-12 on 2023/12/04 + Converted with haproxy-dconv v0.4.2-12 on 2023/12/05

@@ -625,7 +625,7 @@

Management Guide

-

version 2.9-dev12-21

+

version 3.0-dev0


@@ -1184,8 +1184,8 @@

Summary

enables all trace sources on error level. This can notably be useful to detect protocol violations from clients or servers. An optional argument can be used to specify a list of various trace configurations using ',' as - separator. Each element activates one or all trace sources. Additionnaly, - level and verbosity can be optionaly specified on each element using ':' as + separator. Each element activates one or all trace sources. Additionally, + level and verbosity can be optionally specified on each element using ':' as inner separator with trace name. -m <limit> : limit the total allocatable memory to <limit> megabytes across @@ -3305,8 +3305,8 @@

9.3.< names. The report precisely indicates what exact character violated the protocol. Other important information such as the exact date the error was detected, frontend and backend names, the server name (when known), the -internal session ID and the source address which has initiated the session -are reported too. +internal transaction ID and the source address which has initiated the +session are reported too. All characters are returned, and non-printable characters are encoded. The most common ones (\t = 9, \n = 10, \r = 13 and \e = 27) are encoded as one @@ -3341,11 +3341,11 @@

9.3.< In the example above, we see that the backend "http-in" which has internal ID 2 has blocked an invalid response from its server s2 which has internal -ID 1. The request was on session 54 initiated by source 127.0.0.1 and -received by frontend fe-eth0 whose ID is 1. The total response length was -213 bytes when the error was detected, and the error was at byte 23. This -is the slash ('/') in header name "header/bizarre", which is not a valid -HTTP character for a header name. +ID 1. The request was on transaction 54 (called "session" here) initiated +by source 127.0.0.1 and received by frontend fe-eth0 whose ID is 1. The +total response length was 213 bytes when the error was detected, and the +error was at byte 23. This is the slash ('/') in header name +"header/bizarre", which is not a valid HTTP character for a header name.

show events [<sink>] [-w] [-n]
With no option, this lists all known event sinks and their types. With an
 option, it will dump all available events in the designated sink if it is of
@@ -3760,22 +3760,22 @@ 
9.3.<
    srv_check_addr:              Server health check address.
    srv_agent_addr:              Server health agent address.
    srv_agent_port:              Server health agent port.
-
show sess
Dump all known sessions. Avoid doing this on slow connections as this can
-be huge. This command is restricted and can only be issued on sockets
-configured for levels "operator" or "admin". Note that on machines with
-quickly recycled connections, it is possible that this output reports less
-entries than really exist because it will dump all existing sessions up to
-the last one that was created before the command was entered; those which
-die in the mean time will not appear.
-
show sess <id> | older <age> | susp | all
Display a lot of internal information about the matching sessions. In the
-first form, only the session matching the specified session identifier will
+
show sess
Dump all known active streams (formerly called "sessions"). Avoid doing this
+on slow connections as this can be huge. This command is restricted and can
+only be issued on sockets configured for levels "operator" or "admin". Note
+that on machines with quickly recycled connections, it is possible that this
+output reports less entries than really exist because it will dump all
+existing streams up to the last one that was created before the command was
+entered; those which die in the mean time will not appear.
+
show sess <id> | older <age> | susp | all
Display a lot of internal information about the matching streams. In the
+first form, only the stream matching the specified stream identifier will
 be shown. This identifier is the first field at the beginning of the lines in
-the dumps of "show sess" (it corresponds to the session pointer). In the
-second form, only sessions older than <age> (in seconds by default) will be
+the dumps of "show sess" (it corresponds to the stream pointer). In the
+second form, only streams older than <age> (in seconds by default) will be
 shown. Passing "susp" instead will only report entries that are considered as
 suspicious by the developers based on criteria that may in time or vary along
-versions. If "all" is used instead, then all sessions will be dumped. Dumping
-many sessions can produce a huge output, take a lot of time and be CPU
+versions. If "all" is used instead, then all streams will be dumped. Dumping
+many streams can produce a huge output, take a lot of time and be CPU
 intensive, so it's always better to only dump the minimum needed. Those
 information are useless to most users but may be used by haproxy developers
 to troubleshoot a complex bug. The output format is intentionally not
@@ -4355,15 +4355,15 @@ 
9.3.<
 
 This command is restricted and can only be issued on sockets configured for
 level "admin".
-
shutdown session <id>
Immediately terminate the session matching the specified session identifier.
+
shutdown session <id>
Immediately terminate the stream matching the specified stream identifier.
 This identifier is the first field at the beginning of the lines in the dumps
-of "show sess" (it corresponds to the session pointer). This can be used to
-terminate a long-running session without waiting for a timeout or when an
-endless transfer is ongoing. Such terminated sessions are reported with a 'K'
+of "show sess" (it corresponds to the stream pointer). This can be used to
+terminate a long-running stream without waiting for a timeout or when an
+endless transfer is ongoing. Such terminated streams are reported with a 'K'
 flag in the logs.
-
shutdown sessions server <backend>/<server>
Immediately terminate all the sessions attached to the specified server. This
-can be used to terminate long-running sessions after a server is put into
-maintenance mode, for instance. Such terminated sessions are reported with a
+
shutdown sessions server <backend>/<server>
Immediately terminate all the streams attached to the specified server. This
+can be used to terminate long-running streams after a server is put into
+maintenance mode, for instance. Such terminated streams are reported with a
 'K' flag in the logs.
trace
The "trace" command alone lists the trace sources, their current status, and
 their brief descriptions. It is only meant as a menu to enter next levels,
@@ -4597,7 +4597,7 @@ 
experimental-mode" in Section 9.3 and "mcli-debug-mode" in 9.4.1.
hard-reload
This command does the same as the "reload" command over the master CLI with
-the expection that it does a hard-stop (-st) instead of a stop-stop (-sf) of
+the exception that it does a hard-stop (-st) instead of a stop-stop (-sf) of
 the previous process. This means the previous process does not wait to
 achieve anything before exiting, so all connections will be closed.
 
@@ -5026,7 +5026,7 @@ 

 						

 						

-							HAProxy 2.9-dev12-21 – Management Guide

+							HAProxy 3.0-dev0 – Management Guide

 							,