mirrors/haproxy
1
0
Fork 0
mirror of https://git.haproxy.org/git/haproxy.git/ synced 2025-08-11 09:37:20 +02:00
Code Issues Projects Releases Wiki Activity

DOC: http header capture has not been limited in size for a long time

Browse Source 
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.
This commit is contained in:
Willy Tarreau 2012-11-22 00:21:46 +01:00
parent 193b8c6168
commit 0900abb2c3
1 changed files with 10 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
doc/configuration.txt
View File

@ -1788,10 +1788,11 @@ capture request header <name> len <length>
you log if you know your log parser is not smart enough to rely on the you log if you know your log parser is not smart enough to rely on the
braces. braces.
There is no limit to the number of captured request headers, but each capture There is no limit to the number of captured request headers nor to their
is limited to 64 characters. In order to keep log format consistent for a length, though it is wise to keep them low to limit memory usage per session.
same frontend, header captures can only be declared in a frontend. It is not In order to keep log format consistent for a same frontend, header captures
possible to specify a capture in a "defaults" section. can only be declared in a frontend. It is not possible to specify a capture
in a "defaults" section.
Example: Example:
capture request header Host len 15 capture request header Host len 15
@ -1826,10 +1827,11 @@ capture response header <name> len <length>
header which indicates how many bytes are expected to be returned, the header which indicates how many bytes are expected to be returned, the
"Location" header to track redirections. "Location" header to track redirections.
There is no limit to the number of captured response headers, but each There is no limit to the number of captured response headers nor to their
capture is limited to 64 characters. In order to keep log format consistent length, though it is wise to keep them low to limit memory usage per session.
for a same frontend, header captures can only be declared in a frontend. It In order to keep log format consistent for a same frontend, header captures
is not possible to specify a capture in a "defaults" section. can only be declared in a frontend. It is not possible to specify a capture
in a "defaults" section.
Example: Example:
capture response header Content-length len 9 capture response header Content-length len 9