+--On 28 mai 2010 09:02:51 +0200 Knut Arne Bjørndal <[email protected]> wrote: | On 27. mai 2010, at 19.02, Mathieu Arnold wrote: |> +--On 27 mai 2010 17:35:53 +0200 Florian Lohoff <[email protected]> wrote: |> | On Thu, May 27, 2010 at 05:30:51PM +0200, Mathieu Arnold wrote: |> |> |> |> As I said, haproxy is a reverse proxy, it sends the requets it gets |> |> as it gets it, your server is now up in the load balancer. (It does |> |> add a x-forwarded-for header with the original IP.) |> |> |> | |> | The point is that this would be okay - but your alive tests neither |> | request from trapi.osm.lab.rfc822.org nor api1.osm.absolight.net but |> | the systems hostname - which means that the alive checks get into the |> | default Server vhost. |> |> Hum, I see your point. |> What I don't see, is how I could tell haproxy that it should do it that |> way. I'll try and reread the documentation :-) | | | Not exactly very straight forward, but according to the docs it should be | possible. Here from the 1.3 docs:
Oh, wicked, will do :-) -- Mathieu Arnold _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/listinfo/tilesathome
