Workers SDK Issue Reports

← Back to Dashboard

#9599 Missing charset in Content-Type header for workers static assets when deployed

Recommendation:KEEP OPEN
Difficulty:n/a
Reasoning:

Maintainer confirmed production behavior is correct; local dev will be updated to match. Issue serves as tracking for pending local dev fix.

Suggested Action:

Keep open - awaiting fix implementation

View on GitHub →

Analysis Report

Issue Review: cloudflare/workers-sdk#9599

Summary

Missing charset in Content-Type header for static assets on Workers.dev vs local dev - confirmed by maintainer as expected production behavior, local dev will be updated.

Findings

  • Created: 2025-06-13
  • Updated: 2025-06-30
  • Version: Wrangler 4.20.0
  • Component: Static Assets (Workers/Wrangler)
  • Labels: bug
  • Comments: 1

Key Evidence

  • Issue reports Content-Type: text/plain; charset=utf-8 in local dev but Content-Type: text/plain (no charset) when deployed to workers.dev
  • Maintainer @edmundhung confirmed (2025-06-30) that production behavior is correct and local dev will be updated to match
  • No merged PRs or open PRs address this issue yet
  • Issue not mentioned in wrangler changelog
  • This is a local dev parity issue, not a production bug

Recommendation

Status: KEEP OPEN

Reasoning: A Cloudflare maintainer has acknowledged this issue and confirmed the intended fix direction: local development behavior will be updated to match production (removing charset from Content-Type). The issue serves as valid tracking for this pending work.

Action: Keep open as tracking. No further action required until the fix is implemented.

Suggested Comment

N/A - Maintainer has already responded and acknowledged the issue.

Notes & Feedback (0)

No notes yet.

Add Note