------------------------------------------------------------------------
*From: *hushmeh...@hushmail.com
*Sent: * 2013-10-23 01:06:24 E
*To: *hapr...@stormcloud9.net
*CC: *haproxy@formilux.org
*Subject: *Re: handling hundreds of reqrep statements
>
> On Wed, 23 Oct 2013 05:33:38 +0200 "Patrick Hemmer"
> <hapr...@stormcloud9.net> wrote:
>> reqrep ^(GET)\ /foo/(.*) \1\ /foo/\2\r\nX-Header-ID:\ bar if
>> !rewrite-found
> What about reqadd? Clumsy fiddling with \r\n (or \n\r) in regexp
> seems awkward to me.
> reqadd X-Header-ID:\ bar unless rewrite-found
Ya, I think I figured out the issue. Had to do with haproxy
pre-allocating buffers for each header, and not expecting them being
moved around.
Unfortunately I can't use reqadd to add a header as reqadd happens too
late in the process. All reqrep statements happen before reqadd. So if I
put an acl on reqrep to skip it if the header has been added, it'll
always run the reqrep because the header gets added afterwards.
However I think I can use http-request set-header instead of reqadd.
It's not as simple as the reqrep \r\n idea, but still better than the
nasty stick table.
