From: Willy Tarreau Date: Sun, 10 May 2009 11:12:33 +0000 (+0200) Subject: [DOC] rearrange the configuration manual and add a summary X-Git-Tag: v1.3.18~8 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=c57f0e264f8b3a97cc68166359b2b42d66bad2c8;p=thirdparty%2Fhaproxy.git [DOC] rearrange the configuration manual and add a summary Several people have asked for a summary in order to ease finding of sections in the configuration manual. It was the opportunity to tidy it up a bit and rearrange some sections. --- diff --git a/doc/configuration.txt b/doc/configuration.txt index 87bbc857d9..3545b29583 100644 --- a/doc/configuration.txt +++ b/doc/configuration.txt @@ -10,12 +10,314 @@ This document covers the configuration language as implemented in the version specified above. It does not provide any hint, example or advice. For such documentation, please refer to the Reference Manual or the Architecture Manual. +The summary below is meant to help you search sections by name and navigate +through the document. + +Note to documentation contributors : + This document is formated with 80 columns per line, with even number of + spaces for indentation and without tabs. Please follow these rules strictly + so that it remains easily printable everywhere. If a line needs to be + printed verbatim and does not fit, please end each line with a backslash + ('\') and continue on next line. If you add sections, please update the + summary below for easier searching. + + +Summary +------- + +1. Quick reminder about HTTP +1.1. The HTTP transaction model +1.2. HTTP request +1.2.1. The Request line +1.2.2. The request headers +1.3. HTTP response +1.3.1. The Response line +1.3.2. The response headers + +2. Configuring HAProxy +2.1. Configuration file format +2.2. Time format + +3. Global parameters +3.1. Process management and security +3.2. Performance tuning +3.3. Debugging + +4. Proxies +4.1. Proxy keywords matrix +4.2. Alphabetically sorted keywords reference + +5. Server options + +6. HTTP header manipulation + +7. Using ACLs +7.1. Matching integers +7.2. Matching strings +7.3. Matching regular expressions (regexes) +7.4. Matching IPv4 addresses +7.5. Available matching criteria +7.5.1. Matching at Layer 4 and below +7.5.2. Matching contents at Layer 4 +7.5.3. Matching at Layer 7 +7.6. Pre-defined ACLs +7.7. Using ACLs to form conditions + +8. Logging +8.1. Log levels +8.2. Log formats +8.2.1. Default log format +8.2.2. TCP log format +8.2.3. HTTP log format +8.3. Advanced logging options +8.3.1. Disabling logging of external tests +8.3.2. Logging before waiting for the session to terminate +8.3.3. Raising log level upon errors +8.3.4. Disabling logging of successful connections +8.4. Timing events +8.5. Session state at disconnection +8.6. Non-printable characters +8.7. Capturing HTTP cookies +8.8. Capturing HTTP headers +8.9. Examples of logs + +9. Statistics and monitoring +9.1. CSV format +9.2. Unix Socket commands + + +1. Quick reminder about HTTP +---------------------------- + +When haproxy is running in HTTP mode, both the request and the response are +fully analyzed and indexed, thus it becomes possible to build matching criteria +on almost anything found in the contents. + +However, it is important to understand how HTTP requests and responses are +formed, and how HAProxy decomposes them. It will then become easier to write +correct rules and to debug existing configurations. + + +1.1. The HTTP transaction model +------------------------------- + +The HTTP protocol is transaction-driven. This means that each request will lead +to one and only one response. Traditionnally, a TCP connection is established +from the client to the server, a request is sent by the client on the +connection, the server responds and the connection is closed. A new request +will involve a new connection : + + [CON1] [REQ1] ... [RESP1] [CLO1] [CON2] [REQ2] ... [RESP2] [CLO2] ... + +In this mode, called the "HTTP close" mode, there are as many connection +establishments as there are HTTP transactions. Since the connection is closed +by the server after the response, the client does not need to know the content +length. + +Due to the transactional nature of the protocol, it was possible to improve it +to avoid closing a connection between two subsequent transactions. In this mode +however, it is mandatory that the server indicates the content length for each +response so that the client does not wait indefinitely. For this, a special +header is used: "Content-length". This mode is called the "keep-alive" mode : + + [CON] [REQ1] ... [RESP1] [REQ2] ... [RESP2] [CLO] ... + +Its advantages are a reduced latency between transactions, and less processing +power required on the server side. It is generally better than the close mode, +but not always because the clients often limit their concurrent connections to +a smaller value. HAProxy currently does not support the HTTP keep-alive mode, +but knows how to transform it to the close mode. + +A last improvement in the communications is the pipelining mode. It still uses +keep-alive, but the client does not wait for the first response to send the +second request. This is useful for fetching large number of images composing a +page : + + [CON] [REQ1] [REQ2] ... [RESP1] [RESP2] [CLO] ... + +This can obviously have a tremendous benefit on performance because the network +latency is eliminated between subsequent requests. Many HTTP agents do not +correctly support pipelining since there is no way to associate a response with +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. + +Right now, HAProxy only supports the first mode (HTTP close) if it needs to +process the request. This means that for each request, there will be one TCP +connection. If keep-alive or pipelining are required, HAProxy will still +support them, but will only see the first request and the first response of +each transaction. While this is generally problematic with regards to logs, +content switching or filtering, it most often causes no problem for persistence +with cookie insertion. + + +1.2. HTTP request +----------------- + +First, let's consider this HTTP request : + + Line Contents + number + 1 GET /serv/login.php?lang=en&profile=2 HTTP/1.1 + 2 Host: www.mydomain.com + 3 User-agent: my small browser + 4 Accept: image/jpeg, image/gif + 5 Accept: image/png + + +1.2.1. The Request line +----------------------- + +Line 1 is the "request line". It is always composed of 3 fields : + + - a METHOD : GET + - a URI : /serv/login.php?lang=en&profile=2 + - a version tag : HTTP/1.1 + +All of them are delimited by what the standard calls LWS (linear white spaces), +which are commonly spaces, but can also be tabs or line feeds/carriage returns +followed by spaces/tabs. The method itself cannot contain any colon (':') and +is limited to alphabetic letters. All those various combinations make it +desirable that HAProxy performs the splitting itself rather than leaving it to +the user to write a complex or inaccurate regular expression. + +The URI itself can have several forms : + + - A "relative URI" : + + /serv/login.php?lang=en&profile=2 + + It is a complete URL without the host part. This is generally what is + received by servers, reverse proxies and transparent proxies. + + - An "absolute URI", also called a "URL" : + + http://192.168.0.12:8080/serv/login.php?lang=en&profile=2 + + It is composed of a "scheme" (the protocol name followed by '://'), a host + name or address, optionally a colon (':') followed by a port number, then + a relative URI beginning at the first slash ('/') after the address part. + This is generally what proxies receive, but a server supporting HTTP/1.1 + must accept this form too. + + - a star ('*') : this form is only accepted in association with the OPTIONS + method and is not relayable. It is used to inquiry a next hop's + capabilities. + + - an address:port combination : 192.168.0.12:80 + This is used with the CONNECT method, which is used to establish TCP + tunnels through HTTP proxies, generally for HTTPS, but sometimes for + other protocols too. + +In a relative URI, two sub-parts are identified. The part before the question +mark is called the "path". It is typically the relative path to static objects +on the server. The part after the question mark is called the "query string". +It is mostly used with GET requests sent to dynamic scripts and is very +specific to the language, framework or application in use. + + +1.2.2. The request headers +-------------------------- + +The headers start at the second line. They are composed of a name at the +beginning of the line, immediately followed by a colon (':'). Traditionally, +an LWS is added after the colon but that's not required. Then come the values. +Multiple identical headers may be folded into one single line, delimiting the +values with commas, provided that their order is respected. This is commonly +encountered in the "Cookie:" field. A header may span over multiple lines if +the subsequent lines begin with an LWS. In the example in 1.2, lines 4 and 5 +define a total of 3 values for the "Accept:" header. + +Contrary to a common mis-conception, header names are not case-sensitive, and +their values are not either if they refer to other header names (such as the +"Connection:" header). + +The end of the headers is indicated by the first empty line. People often say +that it's a double line feed, which is not exact, even if a double line feed +is one valid form of empty line. + +Fortunately, HAProxy takes care of all these complex combinations when indexing +headers, checking values and counting them, so there is no reason to worry +about the way they could be written, but it is important not to accuse an +application of being buggy if it does unusual, valid things. + +Important note: + As suggested by RFC2616, HAProxy normalizes headers by replacing line breaks + in the middle of headers by LWS in order to join multi-line headers. This + is necessary for proper analysis and helps less capable HTTP parsers to work + correctly and not to be fooled by such complex constructs. + + +1.3. HTTP response +------------------ + +An HTTP response looks very much like an HTTP request. Both are called HTTP +messages. Let's consider this HTTP response : + + Line Contents + number + 1 HTTP/1.1 200 OK + 2 Content-length: 350 + 3 Content-Type: text/html + + +1.3.1. The Response line +------------------------ + +Line 1 is the "response line". It is always composed of 3 fields : + + - a version tag : HTTP/1.1 + - a status code : 200 + - a reason : OK + +The status code is always 3-digit. The first digit indicates a general status : + - 2xx = OK, content is following (eg: 200, 206) + - 3xx = OK, no content following (eg: 302, 304) + - 4xx = error caused by the client (eg: 401, 403, 404) + - 5xx = error caused by the server (eg: 500, 502, 503) + +Please refer to RFC2616 for the detailed meaning of all such codes. The +"reason" field is just a hint, but is not parsed by clients. Anything can be +found there, but it's a common practice to respect the well-established +messages. It can be composed of one or multiple words, such as "OK", "Found", +or "Authentication Required". + +Haproxy may emit the following status codes by itself : + + Code When / reason + 200 access to stats page, and when replying to monitoring requests + 301 when performing a redirection, depending on the configured code + 302 when performing a redirection, depending on the configured code + 303 when performing a redirection, depending on the configured code + 400 for an invalid or too large request + 401 when an authentication is required to perform the action (when + accessing the stats page) + 403 when a request is forbidden by a "block" ACL or "reqdeny" filter + 408 when the request timeout strikes before the request is complete + 500 when haproxy encounters an unrecoverable internal error, such as a + memory allocation failure, which should never happen + 502 when the server returns an empty, invalid or incomplete response, or + when an "rspdeny" filter blocks the response. + 503 when no server was available to handle the request, or in response to + monitoring requests which match the "monitor fail" condition + 504 when the response timeout strikes before the server responds + +The error 4xx and 5xx codes above may be customized (see "errorloc" in section +4.2). + -Note to documentation contributors : this document is formated with 80 columns -per line, with even number of spaces for indentation and without tabs. Please -follow these rules strictly so that it remains easily printable everywhere. If -a line needs to be printed verbatim and does not fit, please end each line with -a backslash ('\') and continue on next line. +1.3.2. The response headers +--------------------------- + +Response headers work exactly like request headers, and as such, HAProxy uses +the same parsing function for both. Please refer to paragraph 1.2.2 for more +details. + + +2. Configuring HAProxy +---------------------- + +2.1. Configuration file format +------------------------------ HAProxy's configuration process involves 3 major sources of parameters : @@ -30,6 +332,10 @@ delimited by spaces. If spaces have to be entered in strings, then they must be preceeded by a backslash ('\') to be escaped. Backslashes also have to be escaped by doubling them. + +2.2. Time format +---------------- + Some parameters involve values representating time, such as timeouts. These values are generally expressed in milliseconds (unless explicitly stated otherwise) but may be expressed in any other unit by suffixing the unit to the @@ -44,7 +350,7 @@ for every keyword. Supported units are : - d : days. 1d = 24h = 1440m = 86400s = 86400000ms -1. Global parameters +3. Global parameters -------------------- Parameters in the "global" section are process-wide and often OS-specific. They @@ -83,7 +389,7 @@ The following keywords are supported in the "global" section : - quiet -1.1) Process management and security +3.1. Process management and security ------------------------------------ chroot @@ -191,7 +497,7 @@ user See also "uid" and "group". -1.2) Performance tuning +3.2. Performance tuning ----------------------- maxconn @@ -265,8 +571,8 @@ tune.maxpollevents tends to trade latency for slightly increased bandwidth. -1.3) Debugging ---------------- +3.3. Debugging +-------------- debug Enables debug mode which dumps to stdout all exchanges, and disables forking @@ -279,7 +585,7 @@ quiet line argument "-q". -2) Proxies +4. Proxies ---------- Proxy configuration can be located in a set of sections : @@ -320,243 +626,16 @@ modifying, or removing arbitrary contents in requests or responses, based on arbitrary criteria. -2.1) Quick reminder about HTTP ------------------------------- - -When a proxy is running in HTTP mode, both the request and the response are -fully analyzed and indexed, thus it becomes possible to build matching criteria -on almost anything found in the contents. - -However, it is important to understand how HTTP requests and responses are -formed, and how HAProxy decomposes them. It will then become easier to write -correct rules and to debug existing configurations. - - -2.1.1) The HTTP transaction model ---------------------------------- - -The HTTP protocol is transaction-driven. This means that each request will lead -to one and only one response. Traditionnally, a TCP connection is established -from the client to the server, a request is sent by the client on the -connection, the server responds and the connection is closed. A new request -will involve a new connection : - - [CON1] [REQ1] ... [RESP1] [CLO1] [CON2] [REQ2] ... [RESP2] [CLO2] ... +4.1. Proxy keywords matrix +-------------------------- -In this mode, called the "HTTP close" mode, there are as many connection -establishments as there are HTTP transactions. Since the connection is closed -by the server after the response, the client does not need to know the content -length. - -Due to the transactional nature of the protocol, it was possible to improve it -to avoid closing a connection between two subsequent transactions. In this mode -however, it is mandatory that the server indicates the content length for each -response so that the client does not wait indefinitely. For this, a special -header is used: "Content-length". This mode is called the "keep-alive" mode : - - [CON] [REQ1] ... [RESP1] [REQ2] ... [RESP2] [CLO] ... - -Its advantages are a reduced latency between transactions, and less processing -power required on the server side. It is generally better than the close mode, -but not always because the clients often limit their concurrent connections to -a smaller value. HAProxy currently does not support the HTTP keep-alive mode, -but knows how to transform it to the close mode. - -A last improvement in the communications is the pipelining mode. It still uses -keep-alive, but the client does not wait for the first response to send the -second request. This is useful for fetching large number of images composing a -page : - - [CON] [REQ1] [REQ2] ... [RESP1] [RESP2] [CLO] ... - -This can obviously have a tremendous benefit on performance because the network -latency is eliminated between subsequent requests. Many HTTP agents do not -correctly support pipelining since there is no way to associate a response with -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. - -Right now, HAProxy only supports the first mode (HTTP close) if it needs to -process the request. This means that for each request, there will be one TCP -connection. If keep-alive or pipelining are required, HAProxy will still -support them, but will only see the first request and the first response of -each transaction. While this is generally problematic with regards to logs, -content switching or filtering, it most often causes no problem for persistence -with cookie insertion. - - -2.1.2) HTTP request -------------------- - -First, let's consider this HTTP request : - - Line Contents - number - 1 GET /serv/login.php?lang=en&profile=2 HTTP/1.1 - 2 Host: www.mydomain.com - 3 User-agent: my small browser - 4 Accept: image/jpeg, image/gif - 5 Accept: image/png - - -2.1.2.1) The Request line -------------------------- - -Line 1 is the "request line". It is always composed of 3 fields : - - - a METHOD : GET - - a URI : /serv/login.php?lang=en&profile=2 - - a version tag : HTTP/1.1 - -All of them are delimited by what the standard calls LWS (linear white spaces), -which are commonly spaces, but can also be tabs or line feeds/carriage returns -followed by spaces/tabs. The method itself cannot contain any colon (':') and -is limited to alphabetic letters. All those various combinations make it -desirable that HAProxy performs the splitting itself rather than leaving it to -the user to write a complex or inaccurate regular expression. - -The URI itself can have several forms : - - - A "relative URI" : - - /serv/login.php?lang=en&profile=2 - - It is a complete URL without the host part. This is generally what is - received by servers, reverse proxies and transparent proxies. - - - An "absolute URI", also called a "URL" : - - http://192.168.0.12:8080/serv/login.php?lang=en&profile=2 - - It is composed of a "scheme" (the protocol name followed by '://'), a host - name or address, optionally a colon (':') followed by a port number, then - a relative URI beginning at the first slash ('/') after the address part. - This is generally what proxies receive, but a server supporting HTTP/1.1 - must accept this form too. - - - a star ('*') : this form is only accepted in association with the OPTIONS - method and is not relayable. It is used to inquiry a next hop's - capabilities. - - - an address:port combination : 192.168.0.12:80 - This is used with the CONNECT method, which is used to establish TCP - tunnels through HTTP proxies, generally for HTTPS, but sometimes for - other protocols too. - -In a relative URI, two sub-parts are identified. The part before the question -mark is called the "path". It is typically the relative path to static objects -on the server. The part after the question mark is called the "query string". -It is mostly used with GET requests sent to dynamic scripts and is very -specific to the language, framework or application in use. - - -2.1.2.2) The request headers ----------------------------- - -The headers start at the second line. They are composed of a name at the -beginning of the line, immediately followed by a colon (':'). Traditionally, -an LWS is added after the colon but that's not required. Then come the values. -Multiple identical headers may be folded into one single line, delimiting the -values with commas, provided that their order is respected. This is commonly -encountered in the "Cookie:" field. A header may span over multiple lines if -the subsequent lines begin with an LWS. In the example in 2.1.2, lines 4 and 5 -define a total of 3 values for the "Accept:" header. - -Contrary to a common mis-conception, header names are not case-sensitive, and -their values are not either if they refer to other header names (such as the -"Connection:" header). - -The end of the headers is indicated by the first empty line. People often say -that it's a double line feed, which is not exact, even if a double line feed -is one valid form of empty line. - -Fortunately, HAProxy takes care of all these complex combinations when indexing -headers, checking values and counting them, so there is no reason to worry -about the way they could be written, but it is important not to accuse an -application of being buggy if it does unusual, valid things. - -Important note: - As suggested by RFC2616, HAProxy normalizes headers by replacing line breaks - in the middle of headers by LWS in order to join multi-line headers. This - is necessary for proper analysis and helps less capable HTTP parsers to work - correctly and not to be fooled by such complex constructs. - - -2.1.3) HTTP response --------------------- - -An HTTP response looks very much like an HTTP request. Both are called HTTP -messages. Let's consider this HTTP response : - - Line Contents - number - 1 HTTP/1.1 200 OK - 2 Content-length: 350 - 3 Content-Type: text/html - - -2.1.3.1) The Response line --------------------------- - -Line 1 is the "response line". It is always composed of 3 fields : - - - a version tag : HTTP/1.1 - - a status code : 200 - - a reason : OK - -The status code is always 3-digit. The first digit indicates a general status : - - 2xx = OK, content is following (eg: 200, 206) - - 3xx = OK, no content following (eg: 302, 304) - - 4xx = error caused by the client (eg: 401, 403, 404) - - 5xx = error caused by the server (eg: 500, 502, 503) - -Please refer to RFC2616 for the detailed meaning of all such codes. The -"reason" field is just a hint, but is not parsed by clients. Anything can be -found there, but it's a common practice to respect the well-established -messages. It can be composed of one or multiple words, such as "OK", "Found", -or "Authentication Required". - -Haproxy may emit the following status codes by itself : - - Code When / reason - 200 access to stats page, and when replying to monitoring requests - 301 when performing a redirection, depending on the configured code - 302 when performing a redirection, depending on the configured code - 303 when performing a redirection, depending on the configured code - 400 for an invalid or too large request - 401 when an authentication is required to perform the action (when - accessing the stats page) - 403 when a request is forbidden by a "block" ACL or "reqdeny" filter - 408 when the request timeout strikes before the request is complete - 500 when haproxy encounters an unrecoverable internal error, such as a - memory allocation failure, which should never happen - 502 when the server returns an empty, invalid or incomplete response, or - when an "rspdeny" filter blocks the response. - 503 when no server was available to handle the request, or in response to - monitoring requests which match the "monitor fail" condition - 504 when the response timeout strikes before the server responds - -The error 4xx and 5xx codes above may be customized (see "errorloc" in section -2.2). - - -2.1.3.2) The response headers ------------------------------ - -Response headers work exactly like request headers, and as such, HAProxy uses -the same parsing function for both. Please refer to paragraph 2.1.2.2 for more -details. - - -2.2) Proxy keywords matrix --------------------------- - -The following list of keywords is supported. Most of them may only be used in a -limited set of section types. Some of them are marked as "deprecated" because -they are inherited from an old syntax which may be confusing or functionally -limited, and there are new recommended keywords to replace them. Keywords -listed with [no] can be optionally inverted using the "no" prefix, ex. "no -option contstats". This makes sense when the option has been enabled by default -and must be disabled for a specific instance. +The following list of keywords is supported. Most of them may only be used in a +limited set of section types. Some of them are marked as "deprecated" because +they are inherited from an old syntax which may be confusing or functionally +limited, and there are new recommended keywords to replace them. Keywords +listed with [no] can be optionally inverted using the "no" prefix, ex. "no +option contstats". This makes sense when the option has been enabled by default +and must be disabled for a specific instance. keyword defaults frontend listen backend @@ -681,8 +760,8 @@ use_backend - X X - keyword defaults frontend listen backend -2.2.1) Alphabetically sorted keywords reference ------------------------------------------------ +4.2. Alphabetically sorted keywords reference +--------------------------------------------- This section provides a description of each keyword and its usage. @@ -696,7 +775,7 @@ acl [flags] [operator] ... acl invalid_src src_port 0:1023 acl local_dst hdr(host) -i localhost - See section 2.3 about ACL usage. + See section 7 about ACL usage. appsession len timeout @@ -1018,7 +1097,7 @@ block { if | unless } The HTTP request will be blocked very early in the layer 7 processing if/unless is matched. A 403 error will be returned if the request - is blocked. The condition has to reference ACLs (see section 2.3). This is + is blocked. The condition has to reference ACLs (see section 7). This is typically used to deny access to certain sensible resources if some conditions are met or not met. There is no fixed limit to the number of "block" statements per instance. @@ -1029,7 +1108,7 @@ block { if | unless } acl local_dst hdr(host) -i localhost block if invalid_src || local_dst - See section 2.3 about ACL usage. + See section 7 about ACL usage. capture cookie len @@ -1068,7 +1147,7 @@ capture cookie len capture cookie ASPSESSION len 32 See also : "capture request header", "capture response header" as well as - section 2.6 about logging. + section 8 about logging. capture request header len @@ -1111,7 +1190,7 @@ capture request header len capture request header X-Forwarded-For len 15 capture request header Referrer len 15 - See also : "capture cookie", "capture response header" as well as section 2.6 + See also : "capture cookie", "capture response header" as well as section 8 about logging. @@ -1148,7 +1227,7 @@ capture response header len capture response header Content-length len 9 capture response header Location len 15 - See also : "capture cookie", "capture request header" as well as section 2.6 + See also : "capture cookie", "capture request header" as well as section 8 about logging. @@ -2022,7 +2101,7 @@ no option dontlog-normal complex issues is in the normal logs which will not be logged here. If you need to separate logs, see the "log-separate-errors" option instead. - See also : "log", "dontlognull", "log-separate-errors" and section 2.6 about + See also : "log", "dontlognull", "log-separate-errors" and section 8 about logging. @@ -2048,7 +2127,7 @@ no option dontlognull If this option has been enabled in a "defaults" section, it can be disabled in a specific instance by prepending the "no" keyword before it. - See also : "log", "monitor-net", "monitor-uri" and section 2.6 about logging. + See also : "log", "monitor-net", "monitor-uri" and section 8 about logging. option forceclose @@ -2191,7 +2270,7 @@ no option httpclose yes | yes | yes | yes Arguments : none - As stated in section 2.1, HAProxy does not yes support the HTTP keep-alive + As stated in section 1, HAProxy does not yes support the HTTP keep-alive mode. So by default, if a client communicates with a server in this mode, it will only analyze, log, and process the first request of each connection. To workaround this limitation, it is possible to specify "option httpclose". It @@ -2233,7 +2312,7 @@ option httplog This option may be set either in the frontend or the backend. - See also : section 2.6 about logging. + See also : section 8 about logging. option http_proxy @@ -2287,7 +2366,7 @@ no option log-separate-errors second may log normal traffic to a rotating buffer and only archive smaller error logs. - See also : "log", "dontlognull", "dontlog-normal" and section 2.6 about + See also : "log", "dontlognull", "dontlog-normal" and section 8 about logging. @@ -2321,7 +2400,7 @@ no option logasap static/srv1 9/10/7/14/+30 200 +243 - - ---- 3/1/1/1/0 1/0 \ "GET /image.iso HTTP/1.0" - See also : "option httplog", "capture response header", and section 2.6 about + See also : "option httplog", "capture response header", and section 8 about logging. @@ -2704,7 +2783,7 @@ option tcplog This option may be set either in the frontend or the backend. - See also : "option httplog", and section 2.6 about logging. + See also : "option httplog", and section 8 about logging. option tcpsplice [ experimental ] @@ -2854,7 +2933,7 @@ redirect prefix [code ]