Hello,
What you want to do is a forward proxy.
HAProxy is not able to do this and the coming DNS feature won't allow
it as well.
Why you want to switch from ATS to HAProxy since ATS can do this
easily out of the box?
If you know in advance the server IP address, then there is something
we can
On Tue, Jun 02, 2015 at 01:59:43AM +, Mrunmayi Dhume wrote:
Hello,
Thanks for all your help. Any rough estimate on when the patch for doing DNS
resolutions during runtime with asynchronous methods might be out?
It should be in 1.6-dev2 in the forthcoming days, it just happens that this
Hello,
Thanks for all your help. Any rough estimate on when the patch for doing DNS
resolutions during runtime with asynchronous methods might be out?
-Mrunmayi
On Saturday, May 30, 2015 2:47 AM, Thierry FOURNIER
tfourn...@haproxy.com wrote:
On Sat, 30 May 2015 00:25:59 + (UTC)
Hello Thierry,
This seems to be what we are looking for, however it doesn't seem to work as
expected. When we use your example as is, it seems to fail with a 500 error.
When we switch to using a IP address, it works, so it seems like DNS resolution
is a problem? As per this doc -
On Tue, 26 May 2015 21:39:23 + (UTC)
Mrunmayi Dhume mrunmayi.dh...@yahoo.com wrote:
Thanks for your detailed reply Thierry. While this approach would solve the
aspect of choosing the backend dynamically we still need to explicitly define
each backend server separately in the haproxy
On Fri, 22 May 2015 19:06:59 + (UTC)
Mrunmayi Dhume mrunmayi.dh...@yahoo.com wrote:
Hello,
I am using haproxy-1.6 with Lua. I have a use-case where I want to set the
destination (backend server) very dynamically, based on certain layer 7
information (I am trying to avoid updating
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 22/05/2015 09:06 μμ, Mrunmayi Dhume wrote:
Hello,
I am using haproxy-1.6 with Lua. I have a use-case where I want to
set the destination (backend server) very dynamically, based on
certain layer 7 information (I am trying to avoid
Thanks for your detailed reply Thierry. While this approach would solve the
aspect of choosing the backend dynamically we still need to explicitly define
each backend server separately in the haproxy config file. Our use-case
involves having 100+ backends and we would prefer not to complicate
8 matches
Mail list logo
