HAProxy 未记录所有请求

Question

对于 1.5-dev22 之前的所有 HAProxy 版本，在中使用时mode http，tunnel如果未指定其他“子模式”，则它会在“子模式”下工作。我意识到 HAProxy 中实际上没有“子模式”，但我不确定该如何称呼它。文档只使用‘模式’这个词，但我发现这更加令人困惑......

无论如何，在tunnel“子模式”仅处理第一个请求和响应，其余内容不做任何分析就直接转发。不应使用此模式，因为它会给日志记录和 HTTP 处理带来很多麻烦。

从 1.5-dev22 开始，默认的“子模式”已从更改为tunnel，keep alive这意味着所有请求和响应都将被处理，并且连接在响应和新请求之间保持打开但处于空闲状态。

option http-keep-alive可以通过在前端和后端中使用、option http-tunnel、option httpclose和关键字option http-server-close来更改此设置option forceclose，有效模式（或“子模式”）已在文档中列出。在第 4 节下，有一个表格，其中显示了有效的“子模式”，该模式基于在用于特定连接的前端和后端中设置的选项。

为了完整起见，这里是文档的相关部分，包括表格及其各种“子模式”，因为它在撰写本文时存在（1.5.14）：

In HTTP mode, the processing applied to requests and responses flowing over
a connection depends in the combination of the frontend's HTTP options and
the backend's. HAProxy supports 5 connection modes :

  - KAL : keep alive ("option http-keep-alive") which is the default mode : all
    requests and responses are processed, and connections remain open but idle
    between responses and new requests.

  - TUN: tunnel ("option http-tunnel") : this was the default mode for versions
    1.0 to 1.5-dev21 : only the first request and response are processed, and
    everything else is forwarded with no analysis at all. This mode should not
    be used as it creates lots of trouble with logging and HTTP processing.

  - PCL: passive close ("option httpclose") : exactly the same as tunnel mode,
    but with "Connection: close" appended in both directions to try to make
    both ends close after the first request/response exchange.

  - SCL: server close ("option http-server-close") : the server-facing
    connection is closed after the end of the response is received, but the
    client-facing connection remains open.

  - FCL: forced close ("option forceclose") : the connection is actively closed
    after the end of the response.

The effective mode that will be applied to a connection passing through a
frontend and a backend can be determined by both proxy modes according to the
following matrix, but in short, the modes are symmetric, keep-alive is the
weakest option and force close is the strongest.

                          Backend mode

                | KAL | TUN | PCL | SCL | FCL
            ----+-----+-----+-----+-----+----
            KAL | KAL | TUN | PCL | SCL | FCL
            ----+-----+-----+-----+-----+----
            TUN | TUN | TUN | PCL | SCL | FCL
 Frontend   ----+-----+-----+-----+-----+----
   mode     PCL | PCL | PCL | PCL | FCL | FCL
            ----+-----+-----+-----+-----+----
            SCL | SCL | SCL | FCL | SCL | FCL
            ----+-----+-----+-----+-----+----
            FCL | FCL | FCL | FCL | FCL | FCL

Answer 1

对于 1.5-dev22 之前的所有 HAProxy 版本，在中使用时mode http，tunnel如果未指定其他“子模式”，则它会在“子模式”下工作。我意识到 HAProxy 中实际上没有“子模式”，但我不确定该如何称呼它。文档只使用‘模式’这个词，但我发现这更加令人困惑......

无论如何，在tunnel“子模式”仅处理第一个请求和响应，其余内容不做任何分析就直接转发。不应使用此模式，因为它会给日志记录和 HTTP 处理带来很多麻烦。

从 1.5-dev22 开始，默认的“子模式”已从更改为tunnel，keep alive这意味着所有请求和响应都将被处理，并且连接在响应和新请求之间保持打开但处于空闲状态。

option http-keep-alive可以通过在前端和后端中使用、option http-tunnel、option httpclose和关键字option http-server-close来更改此设置option forceclose，有效模式（或“子模式”）已在文档中列出。在第 4 节下，有一个表格，其中显示了有效的“子模式”，该模式基于在用于特定连接的前端和后端中设置的选项。

为了完整起见，这里是文档的相关部分，包括表格及其各种“子模式”，因为它在撰写本文时存在（1.5.14）：

In HTTP mode, the processing applied to requests and responses flowing over
a connection depends in the combination of the frontend's HTTP options and
the backend's. HAProxy supports 5 connection modes :

  - KAL : keep alive ("option http-keep-alive") which is the default mode : all
    requests and responses are processed, and connections remain open but idle
    between responses and new requests.

  - TUN: tunnel ("option http-tunnel") : this was the default mode for versions
    1.0 to 1.5-dev21 : only the first request and response are processed, and
    everything else is forwarded with no analysis at all. This mode should not
    be used as it creates lots of trouble with logging and HTTP processing.

  - PCL: passive close ("option httpclose") : exactly the same as tunnel mode,
    but with "Connection: close" appended in both directions to try to make
    both ends close after the first request/response exchange.

  - SCL: server close ("option http-server-close") : the server-facing
    connection is closed after the end of the response is received, but the
    client-facing connection remains open.

  - FCL: forced close ("option forceclose") : the connection is actively closed
    after the end of the response.

The effective mode that will be applied to a connection passing through a
frontend and a backend can be determined by both proxy modes according to the
following matrix, but in short, the modes are symmetric, keep-alive is the
weakest option and force close is the strongest.

                          Backend mode

                | KAL | TUN | PCL | SCL | FCL
            ----+-----+-----+-----+-----+----
            KAL | KAL | TUN | PCL | SCL | FCL
            ----+-----+-----+-----+-----+----
            TUN | TUN | TUN | PCL | SCL | FCL
 Frontend   ----+-----+-----+-----+-----+----
   mode     PCL | PCL | PCL | PCL | FCL | FCL
            ----+-----+-----+-----+-----+----
            SCL | SCL | SCL | FCL | SCL | FCL
            ----+-----+-----+-----+-----+----
            FCL | FCL | FCL | FCL | FCL | FCL

HAProxy 未记录所有请求

答案1

相关内容