Hi Justin, On Tue, 03 Jun 2014, 17:56:49 +0200, Justin Rush wrote: > [...] > The following is the output and log entry from a request to port 443: > > $ curl -k https://proxy.prod/health > "OK" > > haproxy[4424]: 10.20.30.40:53283 [03/Jun/2014:15:49:03.097] https-in~ > app.prod/app1 > 455/0/97/4/556 200 147 - - ---- 0/0/0/0/0 0/0 "GET /health HTTP/1.1" > > > The following is an identical curl/output/log, only using port 8080 instead > > $ curl -k https://proxy.prod:8080/health
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. HTH, cheers. l8er manfred
