On Sat, Apr 02, 2011 at 09:31:01AM +0800, Delta Yeh wrote:
> Thanks Ben for you reply.
> Your solution is OK if all the backends are known.
> 
> But what I want is  don't need to config the acl at all, and haproxy will
> proxy the request to the correct backend.
> 
> I know haproxy should be patched.
> 
> Willy,  do you have any plan to add such feature into haproxy?

Not necessarily, though it might not be very difficult either. We
already have the "transparent" mode, which forwards the connection
to the same destination IP as the incoming connection. In fact, you
would need the same feature, but using a header as the destination
IP instead.

I'm realizing that if we implemented the PROXY protocol in nginx as
we did in haproxy and stunnel, you'd have the feature for free, along
with logging and the ability to perform any type of filtering you'd
like, and this without having to add headers.

Maybe we should go that route instead, as it would bring many more
new features by tightly coupling nginx and haproxy.

Regards,
Willy


Reply via email to