ta
TanStack
GitHub
router
Workspace
GitHub
CI Pipeline Executions
Filtered
Runs
Demo
Insights
Compare tasks
Analytics
Sign in
Toggle sidebar
Overview
⌘K
router
Loading workspace stats
Loading workspace insights...
Statistics interval
7 days
30 days
Latest CI Pipeline Executions
Status
Fix filter
Filter
Fuzzy
Filter range
Sort by
Sort by
Start time
Sort ascending
Sort descending
Canceled
7695
8b7eddb7 fix(router-core): preserve percent-encoded URL-unsafe chars in decodeSegment Replace sanitizePathSegment (which stripped control characters) with a re-encode step that keeps WHATWG path percent-encode set characters and control characters in their encoded form after decodeURI. This preserves the existing decodeURI-based approach which correctly handles multi-byte UTF-8 sequences, while fixing the mismatch between the original request URL and the router's internal representation that caused infinite 307 redirect loops on paths containing these characters. Fixes #7587. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
by CDillinger
C
Succeeded
7695
3f909925 fix(router-core): preserve percent-encoded URL-unsafe chars in decodeSegment Replace sanitizePathSegment (which stripped control characters) with a re-encode step that keeps WHATWG path percent-encode set characters and control characters in their encoded form after decodeURI. This preserves the existing decodeURI-based approach which correctly handles multi-byte UTF-8 sequences, while fixing the mismatch between the original request URL and the router's internal representation that caused infinite 307 redirect loops on paths containing these characters. Fixes #7587. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
by CDillinger
C
Failed
7695
Fix ready
→
dd05e5d8 fix(router-core): preserve percent-encoded URL-unsafe chars in decodeSegment Replace sanitizePathSegment (which stripped control characters) with a re-encode step that keeps WHATWG path percent-encode set characters and control characters in their encoded form after decodeURI. This preserves the existing decodeURI-based approach which correctly handles multi-byte UTF-8 sequences, while fixing the mismatch between the original request URL and the router's internal representation that caused infinite 307 redirect loops on paths containing these characters. Fixes #7587. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
by CDillinger
C
Failed
7695
Fix ready
→
00296a36 fix(router-core): preserve percent-encoded URL-unsafe chars in decodeSegment Replace sanitizePathSegment (which stripped control characters) with a re-encode step that keeps WHATWG path percent-encode set characters and control characters in their encoded form after decodeURI. This preserves the existing decodeURI-based approach which correctly handles multi-byte UTF-8 sequences, while fixing the mismatch between the original request URL and the router's internal representation that caused infinite 307 redirect loops on paths containing these characters. Fixes #7587. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
by CDillinger
C
Failed
7695
Fix ready
→
782242e6 fix(router-core): preserve percent-encoded URL-unsafe chars in decodeSegment Replace decodeURI()-based decoding with per-character decoding that preserves the WHATWG URL path percent-encode set ({, }, <, >, ", `) and ASCII control characters (0x00-0x1F, 0x7F) in their encoded form. Previously, decodeSegment decoded these characters and sanitizePathSegment stripped the control chars. This created mismatches between the original request URL and the router's internal representation, causing infinite 307 redirect loops on paths like /%7B%7Btemplate%7D%7D. By keeping these characters encoded, the router's path representation matches what browsers and upstream layers send, eliminating the mismatch that triggered spurious redirects. Fixes #7587. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
by CDillinger
C
Previous
Next