Skip to content

fix(relay): always admit Desktop WebView CORS origins - #3595

Open
Chessing234 wants to merge 1 commit into
block:mainfrom
Chessing234:fix/cors-windows-tauri-origin
Open

fix(relay): always admit Desktop WebView CORS origins#3595
Chessing234 wants to merge 1 commit into
block:mainfrom
Chessing234:fix/cors-windows-tauri-origin

Conversation

@Chessing234

Copy link
Copy Markdown
Contributor

Summary

  • When BUZZ_CORS_ORIGINS is set, always merge tauri://localhost, http://tauri.localhost, and https://tauri.localhost
  • Document those origins in deploy/compose/.env.example
  • Empty allowlist (dev permissive mode) is unchanged

Windows WebView2 uses http://tauri.localhost. Self-host configs built from the compose example or macOS-oriented guides omit it, so Join community fails with a silent "Failed to fetch" and nothing hits the relay logs (#3490).

Test plan

  • Unit tests for merge_desktop_cors_origins (fills Windows origin; leaves empty list alone)
  • Deploy with BUZZ_CORS_ORIGINS=https://buzz.example.com only — OPTIONS from http://tauri.localhost returns ACAO
  • Windows Desktop Join community against that relay succeeds

Fixes #3490

Made with Cursor

Windows WebView2 uses http://tauri.localhost. When BUZZ_CORS_ORIGINS is
set from the compose example (or a macOS-oriented guide), Join community
fails with a silent Failed to fetch. Merge the fixed Tauri origins into
any non-empty allowlist and document them in .env.example.

Signed-off-by: Taksh <takshkothari09@gmail.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@Chessing234
Chessing234 requested a review from a team as a code owner July 29, 2026 18:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Windows desktop cannot join a self-hosted relay: http://tauri.localhost missing from CORS guidance, fails with a silent "Failed to fetch"

1 participant