{"action":"opened","issue":{"url":"https://api.github.com/repos/tutumcloud/haproxy/issues/167","repository_url":"https://api.github.com/repos/tutumcloud/haproxy","labels_url":"https://api.github.com/repos/tutumcloud/haproxy/issues/167/labels{/name}","comments_url":"https://api.github.com/repos/tutumcloud/haproxy/issues/167/comments","events_url":"https://api.github.com/repos/tutumcloud/haproxy/issues/167/events","html_url":"https://github.com/tutumcloud/haproxy/issues/167","id":146187251,"number":167,"title":"VIRTUAL_HOST_WEIGHT does not provide a fail over for 503","user":{"login":"modius","id":20687,"avatar_url":"https://avatars.githubusercontent.com/u/20687?v=3","gravatar_id":"","url":"https://api.github.com/users/modius","html_url":"https://github.com/modius","followers_url":"https://api.github.com/users/modius/followers","following_url":"https://api.github.com/users/modius/following{/other_user}","gists_url":"https://api.github.com/users/modius/gists{/gist_id}","starred_url":"https://api.github.com/users/modius/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/modius/subscriptions","organizations_url":"https://api.github.com/users/modius/orgs","repos_url":"https://api.github.com/users/modius/repos","events_url":"https://api.github.com/users/modius/events{/privacy}","received_events_url":"https://api.github.com/users/modius/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-04-06T05:04:38Z","updated_at":"2016-04-06T05:04:38Z","closed_at":null,"body":"I'm trying to set up a maintenance page or fall back for when HAPROXY generates a 503.  This is the error that appears if the service is unreachable, and is seen all too often during service restarts and the like.\r\n\r\nI thought using `VIRTUAL_HOST_WEIGHT` would provide a natural failover option, consider:\r\n```\r\nApp1:\r\nVIRTUAL_HOST_WEIGHT=1\r\nVIRTUAL_HOST=app1.example.com\r\n\r\nApp2:\r\nVIRTUAL_HOST_WEIGHT=1\r\nVIRTUAL_HOST=app2.example.com\r\n\r\nCommon:\r\nVIRTUAL_HOST_WEIGHT=-1\r\nVIRTUAL_HOST=*.example.com\r\n```\r\n\r\nSo if either `App1` or `App2` fails and generates a 503 you would hope that `Common` would still serve its maintenance/fallback page -- but it doesn't. If I STOP the `App1` service I just start serving a 503 on `app1.example.com` until such time as its restarted. `Common` never kicks in.\r\n\r\nIs this entirely expected behaviour, and if so, what can we do to set a failover page that shows something other than the standard 503?"}}