The simplest method would be to set up each server to respond to the same
domain name. eg location1, location2, etc would all have the domain '
soap.vendor.com' set up. Then, a user requests soap.vendor.com from the
haproxy load balancer, it gets randomly passed to one of the backends, which
has no problem because it is set up to handle that name
-David R
On Thu, Dec 11, 2008 at 6:25 AM, Jeff Buchbinder < jbuchbinder#ravewireless.com> wrote:
> We were trying to set up a high availability setup for accessing one of our
> vendors' SOAP services, which is located on name based virtual servers.
> Attempting to access any of the sites using the IP address doesn't work
> properly, since they are using HTTP/1.1 name based virtual hosting.
>
> HAproxy doesn't support using FQDN for destination servers, so the only way
> I can figure doing it is using header rewriting to force it to call the
> correct name, but each server has its own slightly different name, like
> location1.vendor.com, location2.vendor.com, etc. Can anyone think of a way
> of doing this that I'm missing?
>
> ------------------
> Jeffrey Buchbinder
> Senior Infrastructure Engineer
> Rave Wireless, Inc
> M: 860 617 5750
> jbuchbinder#ravewireless.com
> ravewireless.com
>
>
Received on 2008/12/11 20:01
This archive was generated by hypermail 2.2.0 : 2008/12/11 20:15 CET