Hi Patrick,
On Tue, May 07, 2013 at 11:37:24PM -0400, Patrick Hemmer wrote:
> With haproxy 1.5, Is there any way to add a dynamic header to the http
> response (like the `http-request add-header` option for request headers)?
> I'm adding a X-Request-Id header to requests before forwarding them on
With haproxy 1.5, Is there any way to add a dynamic header to the http
response (like the `http-request add-header` option for request headers)?
I'm adding a X-Request-Id header to requests before forwarding them on
to the back end, but would also like to be able to send this same header
back in th
Hello Smain,
On Tue, May 07, 2013 at 09:32:17AM +0200, Smain Kahlouch wrote:
> Hello Lukas,
>
> Thanks for your answer.
> Our backend is a webserver providing streaming services.
>
> >From my understanding, the user won't be directed to another backend. It
> will wait till a connection is freed
Hi Eduard,
Im not sure about your iptables rules.. using pf/ipfw on FreeBSD myself...
But to me it looks like those last 4 [SYN] packets should have shown in
a packetcapture on your webserver, unless they are re-routed elsewhere..
You could try a different IP in the source option :
source 0.
I am trying to get HAProxy up and running with TPROXY support...I've built
1.5-dev18 with the proper flags, and I'm running on a kernel with the
correct support.
My config is something like this:
global
log 127.0.0.1 local0 notice
maxconn 200
daemon
defaults
option tcplog
log
Hi David,
thanks for your answer. That´s correct and works. Haproxy starts although not
all vips binding on the host.
Wolfgang
On 5/7/13 7:35 AM, Wolfgang Routschka wrote:
I can only synchronize peer status on running haproxy instances so it´s not
possible to use the same haproxy config file.
On 5/7/13 7:35 AM, Wolfgang Routschka wrote:
I can only synchronize peer status on running haproxy instances so
it´s not possible to use the same haproxy config file. haproxy02
cannot use the haproxy-instance from haproxy01 if there ist broken
because I cannot bind the same VIPs on every host
On 05/05/13 11:19, Hugo Silva wrote:
> To begin with, I forgot to mention that we're on 1.5.d18.
>
> We use inspect-delay for something else (that works), as shown below:
>
>
> backend xmpp-tcp
> modetcp
> source x.x.x.x
>
> option
Hello Lukas,
Thanks for your answer.
Our backend is a webserver providing streaming services.
>From my understanding, the user won't be directed to another backend. It
will wait till a connection is freed :
"Limits the sockets to this number of concurrent connections. Extraneous
connections will
9 matches
Mail list logo