MINOR: logs: don't limit HTTP header captures to HTTP frontends
Similar to previous patches, HTTP header captures are performed when
a TCP frontend switches to an HTTP backend, but are not possible to
report. So let's relax the check to explicitly allow them to be present
in TCP frontends.
diff --git a/doc/configuration.txt b/doc/configuration.txt
index c16137d..89bdf98 100644
--- a/doc/configuration.txt
+++ b/doc/configuration.txt
@@ -12099,10 +12099,10 @@
| | %fi | frontend_ip (accepting address) | IP |
| | %fp | frontend_port (accepting address) | numeric |
| | %ft | frontend_name_transport ('~' suffix for SSL) | string |
- | H | %hr | captured_request_headers default style | string |
- | H | %hrl | captured_request_headers CLF style | string list |
- | H | %hs | captured_response_headers default style | string |
- | H | %hsl | captured_response_headers CLF style | string list |
+ | | %hr | captured_request_headers default style | string |
+ | | %hrl | captured_request_headers CLF style | string list |
+ | | %hs | captured_response_headers default style | string |
+ | | %hsl | captured_response_headers CLF style | string list |
| | %ms | accept date milliseconds | numeric |
| | %pid | PID | numeric |
| H | %r | http_request | string |
@@ -12767,6 +12767,10 @@
request headers block. These blocks are displayed just before the HTTP request
in the logs.
+As a special case, it is possible to specify an HTTP header capture in a TCP
+frontend. The purpose is to enable logging of headers which will be parsed in
+an HTTP backend if the request is then switched to this HTTP backend.
+
Example :
# This instance chains to the outgoing proxy
listen proxy-out