# Configure Backend have different health-check endpoints

**URL:** https://discourse.haproxy.org/t/configure-backend-have-different-health-check-endpoints/4210
**Category:** Help!
**Created:** [August 15, 2019, 9:11pm UTC](https://discourse.haproxy.org/t/configure-backend-have-different-health-check-endpoints/4210 "2019-08-15T21:11:20Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![ashguptak](https://avatars.discourse-cdn.com/v4/letter/a/df788c/32.png) [@ashguptak](https://discourse.haproxy.org/u/ashguptak)
#### Post date: [August 15, 2019, 9:11pm UTC](https://discourse.haproxy.org/t/configure-backend-have-different-health-check-endpoints/4210/1 "2019-08-15T21:11:20Z")

</div>

We are facing a use case where two servers configured for a Backend in HAProxy.cfg file have different health-check endpoints. How can we achieve a successful health check?  
Considered using tcp-check only, but the downside is forwarding requests to servers which are potentially not healthy.

backend all\_envs  
mode http

```
option httpchk GET /abc/system-status
http-check expect status 200
server maui_vip endpt1 weight 99 check ssl // this used above health check path
server aws_test_vip endpt2 weight 1 check // this has a different one (/xyz/actuator/health)
```