Setting root context-path breaks UI

[jpcorreia-promptly]

When running Matchbox in Docker, if I configure the context path to be the root path (/), the UI fails to generate valid requests to the backend.

Steps to reproduce:

1. Start Matchbox with Docker with context-path set to root: docker run --rm --name matchbox -p 8080:8080 -e server.servlet.context-path=/ europe-west6-docker.pkg.dev/ahdis-ch/ahdis/matchbox:v4.0.17 matchbox
2. Open http://localhost:8080/CapabilityStatement
3. Request to backend fails

NOTE: When setting another context path (e.g. docker run --rm --name matchbox -p 8080:8080 -e server.servlet.context-path=/test europe-west6-docker.pkg.dev/ahdis-ch/ahdis/matchbox:v4.0.17 matchbox), everything works fine.

[qligier]

Hi @jpcorreia-promptly! Thank you for your report.

I think server.servlet.context-path doesn't support a trailing slash, although I can't find any official documentation about it. You can run

docker run --rm --name matchbox -p 8080:8080 -e server.servlet.context-path= europe-west6-docker.pkg.dev/ahdis-ch/ahdis/matchbox:v4.0.17 matchbox
# or the maybe safer (depending on your shell)
docker run --rm --name matchbox -p 8080:8080 -e server.servlet.context-path="" europe-west6-docker.pkg.dev/ahdis-ch/ahdis/matchbox:v4.0.17 matchbox

to achieve what you want.