Workers SDK Issue Reports

← Back to Dashboard

#9901 Bug: Cloudflare Vite Plugin with React Router 7 fails when dev server is behind a reverse proxy

Recommendation:NEEDS VERIFICATION
Difficulty:n/a
Reasoning:

Maintainer engaged 2026-01-20 suggesting fix in v1.13.19 (PR #11137). Asked user to upgrade to v1.21.0 and verify. Awaiting response - only 4 days since maintainer comment.

Suggested Action:

Monitor for user response. No immediate action needed.

Analysis Report

Issue Review: cloudflare/workers-sdk#9901

Summary

Cloudflare Vite Plugin crashes with fetch error when dev server is behind a reverse proxy (e.g., nginx).

Findings

  • Created: 2025-07-09
  • Updated: 2026-01-20
  • Version: @cloudflare/vite-plugin 1.9.1 → 1.21.2 (current)
  • Component: vite-plugin-cloudflare
  • Labels: bug, vite-plugin
  • Comments: 2

Key Evidence

  • Maintainer already engaged: @edmundhung responded on 2026-01-20 suggesting the issue may have been fixed in v1.13.19 by PR #11137
  • PR #11137 merged 2025-10-31: Switched all instances of miniflare.getWorker().fetch() to use miniflare.dispatchFetch() for consistent response encoding
  • No explicit fix found: No PR directly references or fixes issue #9901
  • Awaiting user verification: Maintainer asked user to upgrade to v1.21.0, clear node_modules, and report back with nginx config if issue persists
  • Significant version gap: 12 minor versions released since issue was reported (v1.9.1 → v1.21.2)

Error Details

The error occurs in miniflare.dispatchFetch() when the Vite dev server receives requests through a reverse proxy. The root cause is likely related to how the request URL or headers are constructed when forwarded through a proxy.

Recommendation

Status: NEEDS VERIFICATION

Reasoning: A maintainer has already engaged with the issue and believes a fix may be in place. The issue is now in an appropriate "waiting for user response" state. The second commenter (AtelyPham) was asked on 2026-01-20 to upgrade and verify - this is only 4 days old, so reasonable to wait for response.

Action: No immediate action needed. Monitor for user response. If no response after 2-3 weeks, the maintainer's comment can be followed up with a request to close if the issue is no longer relevant.

Suggested Comment

N/A - Maintainer has already appropriately engaged with the issue.

Notes & Feedback (0)

No notes yet.

Add Note