Hi Manfred,
On Tue, Jun 3, 2014 at 11:12 AM, Manfred Hollstein <[email protected]> wrote: > > Can you try if "curl -k http://proxy.prod:8080/health"; works? If I'm not > mistaken, https:// implicitly uses port 443, but don't know how the > explicit :8080 might interfere with that. > As I expected, this gets an empty reply: $ curl -k http://app.prod:8080/health curl: (52) Empty reply from server So, haproxy is definitely listening on 8080 and expecting an SSL client. (Also, I just realized my sanitizing above was wrong, my curl commands are all to "app.prod", not "proxy.prod".)
