Hi,
My question is more about HTTP/REST in general, but I can't think of a
better place to find experts than this mailing list.
Can you share your approaches to providing back pressure with HTTP? I'm
talking about handling cases when upstream service is overloaded due to
increased request rate, o
From 29bddd461c30bc850633350ac81e3c9fd7b56cb8 Mon Sep 17 00:00:00 2001
From: Daniel Schneller
Date: Mon, 21 Mar 2016 20:46:57 +0100
Subject: [PATCH] DOC: Clarify tunes.vars.xxx-max-size settings
Adds a little more clarity to the description of the maximum sizes of
the different variable scopes an
Why not just add each server multiple times with a different src parameter
and a different name.
Something like
backend my_be
mode tcp
server server1_src1 10.1.0.1 source 10.0.0.1
server server1_src2 10.1.0.1 source 10.0.0.2
server server2_src1 10.1.0.2 source 10.0.0.1
server
Hi,
We're trying to find a way to have multiple sources per server and
thus bypass 64k connections per server.
We already tried with SNAT iptables :
iptables -t nat -A POSTROUTING -o eth2 -j SNAT --to 10.0.0.1-10.0.10
without success because kernel is hashing real source ip and real
destination
port 443 sharing, ie nginx + ssh + openvpn (tcp) + JitsiVideoBridge on one
ip/server/port 443
with 'usesrc clientip' the server even see the real client ip
2016-03-20 11:41 GMT+01:00 Unknown User :
> Hi all,
>
> I am interested in knowing some of the use cases people have used haproxy
> for.
> Th
Ha proxiers,
Wondering if it might be possible to have return traffic of transparent L4
proxies seem to come from individual real server or at least leave from same IP
stack as request was received from.
Problem is I’ve got a HA proxy binding to multiple ‘public’ IP stacks with
client transpar
6 matches
Mail list logo