Skip to content

fix(webui): use same-origin API for production route #27

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
thedancingdeveloper merged 1 commit into from
Jul 29, 2026
Merged

fix(webui): use same-origin API for production route #27

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 8 additions & 2 deletions crates/librtbit/webui/src/http-api.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,8 +52,14 @@ const apiUrl = (() => {

const url = new URL(window.location.href);

// assume Vite devserver
if (url.port == "3031" || url.port == "1420") {
// Vite's development server runs on 3031 and forwards API requests to a
// separately running backend on 3030. The production web UI is served by
// rtbit itself under /web/ on the API port, so it must use same-origin API
// requests. The desktop dev shell on 1420 also talks to the backend on 3030.
if (url.port == "3031" && (url.pathname === "/" || url.pathname === "")) {
return `${url.protocol}//${url.hostname}:3030`;
}
if (url.port == "1420") {
return `${url.protocol}//${url.hostname}:3030`;
}

Expand Down
Loading