Re: How does http_find_header() work?

On Thu, Mar 31, 2011 at 08:10:04AM -0400, Roy Smith wrote: > I didn't really write a specification, but I think a critical part of the spec > would be that the only guarantee about the id string is that it's unique It's unique within a delimited perimeter. That's important. In some contexts, it wi

Re: How does http_find_header() work?

On Thu, Mar 31, 2011 at 07:58:53AM -0400, Roy Smith wrote: > Looking at the docs, I see some lines that use "option" and some that don't. > Is there a general rule as to when it should use "option"? Could you give me > a use case where you would want to apply this conditionally? Normally "opti

Re: 403 forbidden errors.

On Thu, Mar 31, 2011 at 04:32:41PM -0600, Don MacArthur wrote: > As a practice, we avoid the use of cookies. Then what does your application use to recognize a client ? Haproxy's cookies are just session cookies, not stored cookies. It can even make use of the application's cookie. > I am load ba

Re: Expire Cookies ??

Hi Joel, On Thu, Mar 31, 2011 at 12:29:27PM -0700, Joel Krauska wrote: > It would be nice to be able to set an expiration timer on server > persistence cookies set by HAProxy. > > A'la: > http://en.wikipedia.org/wiki/HTTP_cookie#Expires_and_Max-Age > > From what I can tell HAProxy is not settin

Re: haproxy 1.4.11 failure on reload on Linux 2.6.38 (but not 2.6.35): "Starting frontend [name]: cannot bind socket"

Hi Charles, On Thu, Mar 31, 2011 at 02:42:54PM -0500, Charles Duffy wrote: > Howdy! I'm having trouble with the haproxy reload command. The below happens > on my VPS vendor's builds of Linux 2.6.38 but not their 2.6.35: > > + /usr/sbin/haproxy -D -f /etc/haproxy/haproxy.cfg -p /var/run/haproxy.pi

Re: HAProxy pconn question

Hi Mike, On Wed, Mar 30, 2011 at 01:12:21PM -0700, Mike Oxford wrote: > >From what I can tell via Docs + The Great Google I see that HAProxy > seems to work in three ways for HTTP/1.1 persistant connections. > > 1) Full keep alive, 1:1 mapped client-server. All requests go to the same > server.

Re: Build error on CentOS 5.5 x86_64 with PCRE support

Good to know, thanks Jeremy. Cheers, Guy On Thu, Mar 31, 2011 at 6:05 PM, Jeremy Hinegardner wrote: > On Thu, Mar 31, 2011 at 10:37:22AM -0700, g...@desgames.com wrote: >> Hi all, >> >> I got an error while trying to build haproxy 1.4 on a system running >> CentOS 5.5 x86_64. I have both the i38

Re: Build error on CentOS 5.5 x86_64 with PCRE support

On Thu, Mar 31, 2011 at 10:37:22AM -0700, g...@desgames.com wrote: > Hi all, > > I got an error while trying to build haproxy 1.4 on a system running > CentOS 5.5 x86_64. I have both the i386 and x86_64 versions of pcre > installed, but if I try to build haproxy using ARCH=x86_64 with PCRE > suppo

Re: 403 forbidden errors.

Thank you very much for taking the time to review my information and give so much detailed feed back! I implemented the changes and the proxy now responds as designed. In production testing I found another item I need to attend to. My original requirements did not include maintaining session aff

haproxy 1.4.11 failure on reload on Linux 2.6.38 (but not 2.6.35): "Starting frontend [name]: cannot bind socket"

Howdy! I'm having trouble with the haproxy reload command. The below happens on my VPS vendor's builds of Linux 2.6.38 but not their 2.6.35: + /usr/sbin/haproxy -D -f /etc/haproxy/haproxy.cfg -p /var/run/haproxy.pid -sf 27913 [ALERT] 089/191251 (27947) : Starting frontend pgsql-master-in: cannot b

Expire Cookies ??

It would be nice to be able to set an expiration timer on server persistence cookies set by HAProxy. A'la: http://en.wikipedia.org/wiki/HTTP_cookie#Expires_and_Max-Age From what I can tell HAProxy is not setting an expires window for cookies. Is this a feature that I just can't find in the doc

Re: Build error on CentOS 5.5 x86_64 with PCRE support

On Thu, Mar 31, 2011 at 1:37 PM, g...@desgames.com wrote: > /usr/bin/ld: skipping incompatible /usr/lib/libpcre.so when searching for > -lpcre > /usr/bin/ld: skipping incompatible /usr/lib/libpcre.a when searching for > -lpcre > It's looking in /usr/lib, which only 32bit. Try forcing it with U

Re: Build error on CentOS 5.5 x86_64 with PCRE support

Hi, do you need shared pcre? if not, try USE_STATIC_PCRE=1 then. Cheers, Kai

Build error on CentOS 5.5 x86_64 with PCRE support

Hi all, I got an error while trying to build haproxy 1.4 on a system running CentOS 5.5 x86_64. I have both the i386 and x86_64 versions of pcre installed, but if I try to build haproxy using ARCH=x86_64 with PCRE support, I get the following errors right at the end of the process: /usr/bin/ld: s

Re: How does http_find_header() work?

My intent was just to have a unique string that could be searched for in the logs. Building it by smashing together the hostid, pid, timestamp, etc, was just a fast hack to get something unique. I made one attempt to compact the string by running it through md5, but then I realized that the mo

Re: How does http_find_header() work?

Looking at the docs, I see some lines that use "option" and some that don't. Is there a general rule as to when it should use "option"? Could you give me a use case where you would want to apply this conditionally? As far as stripping headers, one of the problems is that the unique id inserti

Re: How does http_find_header() work?

Hi, Thx Roxy, this would be very useful to have. I'm just wondering about the id format. If all the "fields" correspond to something meaningful, like host_id, pid, timestamp, etcetera, would it make sense to have them in a more human readable format? Regards, Bart On Thu, Mar 31, 2011 at 4:30 AM

Re: How does http_find_header() work?

This would be useful, but having a format similar to what's currently used for forwardfor would be nice: option uniqueid [{if | unless} ] [ header ] I would also like to be sure that any incoming values for the header could be stripped (using reqidel) and still have the new one added properly.