site:github.com/cloudflare/workerd "invalid redirect value"

TL;DR

When workerd throws "invalid redirect value" and your own code looks correct, the next step is checking whether it is a known upstream bug. Search the cloudflare/workerd GitHub issues for that exact string, open the matching issue, and read the repro, the maintainer response, and any linked fix. Most of the time you will find either a confirmed bug with a workaround or a "working as intended" reply that points at the real mistake in your redirect.

site:github.com/cloudflare/workerd "invalid redirect value"

Steps

1. Search the workerd issue tracker for the exact error string:

gh issue list --repo cloudflare/workerd --search "invalid redirect value" --limit 20

Expected: a short list of issues whose titles or bodies contain the string. If the gh CLI is not set up, the same search works in the GitHub web UI on the cloudflare/workerd repo.

1. Open the top matches and compare the stack trace and repro to yours. Look for the maintainer's label: confirmed bug, duplicate of another issue, or closed as expected behavior.

Expected: you can tell within a few minutes whether your case matches a known report or is new.

1. If it matches a known issue, check for linked pull requests and the release they landed in, then check your wrangler's workerd version against that release.

Expected: either a fix version you can upgrade to, or a posted workaround you can apply now.

1. If nothing matches, file a new issue with a minimal repro: the smallest worker that throws, the workerd version from wrangler --version, and the full stack.

Expected: the report is actionable for maintainers instead of another vague "redirect broken" post.

Use this when

• Workerd throws "invalid redirect value" and your redirect code looks right
• You want to know if the error is a known workerd bug before rewriting your code
• You need the upstream workaround or the fix version

Not for this skill when

• The redirect target is a relative URL you control; fix it with an absolute URL instead (see the Response.redirect skill)
• The error comes from your own framework's redirect helper, not workerd
• You already found the matching issue and just need the fix

Variant phrasings

• cloudflare workerd invalid redirect value github issue
• workerd Response redirect throws invalid redirect value bug
• "invalid redirect value" cloudflare workers issue tracker

Why it happens

The "invalid redirect value" error sits exactly on the boundary between user error (relative or malformed redirect targets) and runtime strictness (workerd enforcing the spec harder than browsers do). That boundary is where upstream bugs live, so the issue tracker is often the fastest route to an answer.

Edge cases

• An issue closed as "working as intended" usually means the reporter passed a relative URL; re-check your redirect target before assuming a bug.
• Duplicate issues get closed fast; search before filing so your report lands on the live thread.
• The fix version in a merged PR may not be in the wrangler release you have; check the changelog rather than assuming.
• Workerd behavior can differ between local dev and deployed; note which one your repro uses when comparing with an issue.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstHiDiNw8tmtxnomR2QGz8w