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:
option httpchk <method> <uri> <version>
...
<version> is the optional HTTP version string. It defaults to "HTTP/1.0"
but some servers might behave incorrectly in HTTP 1.0, so turning
it to HTTP/1.1 may sometimes help. Note that the Host field is
mandatory in HTTP/1.1, and as a trick, it is possible to pass it
after "\r\n" following the version string.
...
option httpchk OPTIONS * HTTP/1.1\r\nHost:\ www
--
Knut Arne Bjørndal
aka Bob Kåre
[email protected]
bobk...@irc
_______________________________________________
Tilesathome mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/tilesathome
