This would be useful, but having a format similar to what's currently
used for forwardfor would be nice:
option uniqueid [{if | unless} condition] [ header name ]
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
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,
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
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:
Hi,
do you need shared pcre? if not, try USE_STATIC_PCRE=1 then.
Cheers,
Kai
On Thu, Mar 31, 2011 at 1:37 PM, g...@desgames.com 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
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
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
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
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
support, I
Good to know, thanks Jeremy.
Cheers,
Guy
On Thu, Mar 31, 2011 at 6:05 PM, Jeremy Hinegardner
jer...@hinegardner.org 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
Hi Mike,
On Wed, Mar 30, 2011 at 01:12:21PM -0700, Mike Oxford wrote:
From what I can tell via Docs + The Great Googletm 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.
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.pid
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 setting an
14 matches
Mail list logo
