# Redirects stuck to default backend

**URL:** <https://discourse.haproxy.org/t/redirects-stuck-to-default-backend/7223>\
**Category:** Help!\
**Created:** [December 17, 2021, 9:34am UTC](https://discourse.haproxy.org/t/redirects-stuck-to-default-backend/7223 "2021-12-17T09:34:54Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![dinceremre](https://avatars.discourse-cdn.com/v4/letter/d/3ab097/32.png) [@dinceremre](https://discourse.haproxy.org/u/dinceremre)\
**Post date:** [December 17, 2021, 9:34am UTC](https://discourse.haproxy.org/t/redirects-stuck-to-default-backend/7223/1 "2021-12-17T09:34:54Z")

</div>

Dear All,  
the acl below works and forwards the request to acl profile\_uri  
however the following requests issued by the first page of the profile app goes to other backends because the app does not know about load balancer paths.  
IS there a way to stick the user to the same backend?

how can i cope with this  
regards  
Emre

defaults  
log global  
mode http  
option httplog  
option dontlognull  
option httpclose

```
    timeout connect 5000
    timeout client 50000
    timeout server 50000

errorfile 400 /etc/haproxy/errors/400.http
errorfile 403 /etc/haproxy/errors/403.http
errorfile 408 /etc/haproxy/errors/408.http
errorfile 500 /etc/haproxy/errors/500.http
errorfile 502 /etc/haproxy/errors/502.http
errorfile 503 /etc/haproxy/errors/503.http
errorfile 504 /etc/haproxy/errors/504.http

```

frontend http\_front  
bind \*:80  
acl profile\_uri path\_beg -i /profile  
use\_backend manfrontend if profile\_uri  
use\_backend http\_rear unless profile\_uri  
default\_backend http\_rear

backend manfrontend  
mode http  
server webC 10.154.22.33:4007

backend http\_rear  
mode http  
server wbs1 10.154.22.33:3000

backend http\_rear  
balance roundrobin  
server [wbs1.com](http://wbs1.com) 10.154.22.33:3000 check

backend manfrontend  
balance roundrobin  
server webC 10.154.22.33:4007 check

```auto

```