Re: handling hundreds of reqrep statements

2013-10-28 Thread Willy Tarreau
Hi Patrick, On Wed, Oct 23, 2013 at 02:15:50AM -0400, Patrick Hemmer wrote: It seems that when the request first comes in, haproxy allocates a buffer for every header. If the header is X-Foo: bar it allocates a 10 character buffer. When you do `reqrep` on the request line, and add a line at

Re: handling hundreds of reqrep statements

2013-10-23 Thread Patrick Hemmer
*From: *Patrick Hemmer hapr...@stormcloud9.net *Sent: * 2013-10-22 23:32:31 E *CC: *haproxy@formilux.org *Subject: *Re: handling hundreds of reqrep statements

Re: handling hundreds of reqrep statements

2013-10-23 Thread Patrick Hemmer
*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

Re: handling hundreds of reqrep statements

2013-10-22 Thread Patrick Hemmer
*From: *Patrick Hemmer hapr...@stormcloud9.net *Sent: * 2013-10-22 19:13:08 E *To: *haproxy@formilux.org *Subject: *handling hundreds of reqrep statements I'm currently using haproxy (1.5-dev19) as a content based router.

Re: handling hundreds of reqrep statements

2013-10-22 Thread hushmehard
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