Get without trailing slash gives HTTP 302 and reveals upstream host

[tisaksen]

Hi

The following GET gives me a HTTP 302 which in turn reveals the upstream host address.

GET /my-service

I noticed that this does not happen if I do the request with a trailing slash:

GET /my-service/

How can I avoid this?

My simple service config:

• name: my-service
  url: http://my-cluster/internal-path/
  routes:
  • name: service-route
    paths:
    • /my-service

Sample output:

curl -v -L https://fake.domain.com/my-service --insecure -H foo:bar -H baz:qux
...
> GET /my-service HTTP/1.1
> Host: fake.domain.com
> User-Agent: curl/7.83.1
> Accept: */*
> foo:bar
> baz:qux
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 302 Moved Temporarily
< Date: Wed, 29 Mar 2023 07:14:47 GMT
< Content-Type: text/html
< Content-Length: 269
< Connection: keep-alive
< Location: http://192.168.10.29:8888/internal-path
...

Working request, with trailing slash:

curl -v -L https://fake.domain.com/my-service --insecure -H foo:bar -H baz:qux
...
> GET /my-service/ HTTP/1.1
> Host: fake.domain.com
> User-Agent: curl/7.83.1
> Accept: */*
...
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK