Hi Brian,
Thanks for your suggestion. Unfortunately it's not clear how I would
use this command and format it when doing a redirect. I read the
HAProxy 1.5 documentation, but it wasn't detailed enough.
You don't want a redirect, you explicitly asked for a rewrite:
retaining original domain
Your listing "HA Proxy" is now available at http://cohesive-networks.com/partners/directory/7699/ha-proxy/ and can be viewed by the public.
Its a feature, a frontend running with tcp can use a backend using http.
If you want both to use tcp either put that in the defaults, or specify
it for both frontendbackend.
It seems to me your assumption that the backend automaticaly takes over
the mode from the frontend is wrong. Perhaps a
I think that nails the problem. So if its not just me then the question is
if this is intended behavior or if its a bug. If its intended then I don't
think its entirely clear from the documentation that 'mode tcp' only works
under certain circumstances. If we confirm that its a bug then I'd be
Hi, yes, we do want a rewrite. The initial request that came to us also
included a request to redirect at the same time, but now that I think about
this (since it's my first time trying to accomplish this) I think we can just
do a rewrite.
EXAMPLE: alias.com alias.com/path (this path is on
Which does not prevent the backend from using mode http as the defaults
section sets.
CJ Ess schreef op 16-6-2015 om 22:36:
mode tcp is already present in mainfrontend definition below the
bind statement
On Mon, Jun 15, 2015 at 3:05 PM, PiBa-NL piba.nl@gmail.com
mode tcp is already present in mainfrontend definition below the bind
statement
On Mon, Jun 15, 2015 at 3:05 PM, PiBa-NL piba.nl@gmail.com wrote:
CJ Ess schreef op 15-6-2015 om 20:52:
This one has me stumped - I'm trying to proxy SMTP connections however I'm
getting an HTTP response
On Mon, Jun 15, 2015 at 02:48:13PM +0200, Lukas Tribus wrote:
Subject: Does haproxy use lt or et mode of epoll ?
thanks
Level-triggered, if I understand the following commit correctly:
http://www.haproxy.org/git?p=haproxy.git;a=commit;h=6c11bd2f89eb043fd493d77b784198e90e0a01b2
Hi list,
Is there any way to log, or report, or notify, or identify any backend
that is not responding, without using explicit health-checks? The
reason for this is that we are planning a big deployment of LB/servers,
something along the lines of:
LB1, LB2, LB100 or more
^
9 matches
Mail list logo
