[Tilesathome] TRAPI down?

[Mathieu Arnold]

+--On 27 mai 2010 17:24:07 +0200 Florian Lohoff <f at zz.de> wrote:
| On Thu, May 27, 2010 at 03:21:31PM +0200, Mathieu Arnold wrote:
|> | API_TRAPI = http://trapi.osm.lab.rfc822.org/api/%v/map?bbox=%b
|> 
|> Hum, the thing is that in the default t at h config, it's : 
|> http://api1.osm.absolight.net/api/%v/map?bbox=%b
| 
| I just cut'n'wasted from my general.conf which i changed to try it out.
| 
|> and haproxy forwards the "Host: api1.osm.absolight.net" http header, so,
|> you'd need to add a server alias to it in your vhost for it to work.
|> After that, your server will appear in green there :
|> http://api1.osm.absolight.net/haproxy?stats
|> and will start getting requests :-)
| 
| You are querying with the alive stuff with a different hostname than when
| forwarding queries:
| 
| bs5.lab.rfc822.org:80 79.143.240.199 - - [27/May/2010:17:22:20 +0200]
| "GET /api/0.6/map?bbox=0,0,0,0 HTTP/1.0" 404 292 "-" "-"
| 
| Typically my "default" host is empty and only the vhosts have their own
| config and directories - so bs5 is empty as the trapi stuff is on the 
| "trapi.osm.lab.rfc822.org" hostname ... I added the api1.osm.absolight.net
| hostalias to the apache though ...

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.)

-- 
Mathieu Arnold