Http-request replace-uri seems to be handled differently between 2.0.9 and 2.1.0

@andi wrote:

Hi everyone

I updated my haproxy from 2.0.9 to 2.1.0 and it seems that http-request replace-uri is handled differently between these two versions.

I’m using the following backend configuration where I use http-request replace-uri (.*) /guacamole\1 to rewrite the document root to /guacamole.

backend guacamole_backend
    balance leastconn
    option http-keep-alive
    option forwardfor
    http-reuse safe
    option httpchk HEAD / HTTP/1.1\r\nHost:\ cloud.foo.bar.de
    http-request set-header X-ORIGIN-URL http://%[hdr(host)]%[path] 
    http-request set-header X-REMOTE-IP %[src]
    http-request replace-uri (.*) /guacamole\1
    default-server inter 2s downinter 5s rise 3 fall 2
    server docker_guacamole 127.0.0.1:8080 check

With version 2.0.9 this works as I expected and the document root is rewritten to /guacamole.
Backend log:

[26/Nov/2019:20:12:34 +0000] "GET /guacamole/ HTTP/1.1" 200 4534
[26/Nov/2019:20:12:34 +0000] "GET /guacamole/relocateParameters.js HTTP/1.1" 200 4505
[26/Nov/2019:20:12:34 +0000] "GET /guacamole/webjars/angular-touch/1.6.9/angular-touch.min.js HTTP/1.1" 200 4074

When I switch to version 2.1.0 the backend logs request like this:

[26/Nov/2019:20:13:28 +0000] "GET /guacamolehttps://cloud.foo.bar.de/ HTTP/1.1" 404 1122
[26/Nov/2019:20:13:28 +0000] "GET /guacamolehttps://cloud.foo.bar.de/favicon.ico HTTP/1.1" 404 1133

Am I using http-request replace-uri the wrong way?

Posts: 1

Participants: 1

Read full topic