From 0900abb2c3c93d8a41e2d7988d65240b496b2938 Mon Sep 17 00:00:00 2001 From: Willy Tarreau Date: Thu, 22 Nov 2012 00:21:46 +0100 Subject: [PATCH] DOC: http header capture has not been limited in size for a long time It's been documented for a very long time that captured HTTP headers were limited to 64 characters, but this has not the case anymore since 1.3.11 in 2007 (commit cf7f320f), as they all use their own pool and have no such limit anymore. This fix should be backported to 1.4 and 1.3. --- doc/configuration.txt | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/doc/configuration.txt b/doc/configuration.txt index fd3e38de6..663ffde13 100644 --- a/doc/configuration.txt +++ b/doc/configuration.txt @@ -1788,10 +1788,11 @@ capture request header len you log if you know your log parser is not smart enough to rely on the braces. - There is no limit to the number of captured request headers, but each capture - is limited to 64 characters. In order to keep log format consistent for a - same frontend, header captures can only be declared in a frontend. It is not - possible to specify a capture in a "defaults" section. + There is no limit to the number of captured request headers nor to their + length, though it is wise to keep them low to limit memory usage per session. + In order to keep log format consistent for a same frontend, header captures + can only be declared in a frontend. It is not possible to specify a capture + in a "defaults" section. Example: capture request header Host len 15 @@ -1826,10 +1827,11 @@ capture response header len header which indicates how many bytes are expected to be returned, the "Location" header to track redirections. - There is no limit to the number of captured response headers, but each - capture is limited to 64 characters. In order to keep log format consistent - for a same frontend, header captures can only be declared in a frontend. It - is not possible to specify a capture in a "defaults" section. + There is no limit to the number of captured response headers nor to their + length, though it is wise to keep them low to limit memory usage per session. + In order to keep log format consistent for a same frontend, header captures + can only be declared in a frontend. It is not possible to specify a capture + in a "defaults" section. Example: capture response header Content-length len 9