[scottjasso]

The default server-list.json that docker generates uses /backend, an absolute path. This breaks reverse proxying -- instead of example.com/speedtest/backend, requests are going to example.com/backend. Simply changing this to relative backend makes reverse proxying work fine.

[qodo-free-for-open-source-projects]

PR Summary by Qodo

Use a relative backend URL in Docker's default server list

🐞 Bug fix 🕐 Less than 5 minutes

AI Description

• Generate a relative backend URL in Docker's default server list.
• Keep backend requests under the application's path when served behind a reverse proxy.

Diagram

graph TD
  A["Docker entrypoint"] --> B["Default server list"] --> C["Browser speed test"] --> D["Reverse proxy"] --> E["Local backend"]

Loading

High-Level Assessment

Use the relative URL in the generated default: it addresses the path-prefix issue at its source without requiring proxy-specific rewrite rules. Mounted server lists and SERVER_LIST_URL remain unaffected.

Files changed (1) +1 / -1

Bug fix (1) +1 / -1

entrypoint.shGenerate a relative local backend URL +1/-1

Generate a relative local backend URL

• Changes the fallback server-list.json entry from '/backend' to 'backend' when no server list or URL is supplied. This lets browser requests resolve beneath the application's path instead of the domain root.

docker/entrypoint.sh

[qodo-free-for-open-source-projects]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Tip of the day

💡 Did you know, you can ask Qodo to dismiss a finding you disagree with, with your reason on record

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

[sstidl]

thank you for pointing that out