c351f6154b
Prior to this pull request, Next.js would immediately decode all URLs sent to its server (via `path-match`). This was rarely needed, and Next.js would typically re-encode the incoming request right away (see all the `encodeURIComponent`s removed in PR diff). This adds unnecessary performance overhead. Long term, this will also help prevent weird encoding edge-cases like #10004, #10022, #11371, et al. --- No new tests are necessary for this change because we've extensively tested these edge cases with existing tests. One test was updated to reflect that we skip decoding in a 404 scenario. Let's see if all the existing tests pass! |
||
---|---|---|
.. | ||
escape-path-delimiters.ts | ||
format-url.ts | ||
get-asset-path-from-route.ts | ||
get-route-from-asset-path.ts | ||
index.ts | ||
is-dynamic.ts | ||
parse-relative-url.ts | ||
path-match.ts | ||
prepare-destination.ts | ||
querystring.ts | ||
resolve-rewrites.ts | ||
route-matcher.ts | ||
route-regex.ts | ||
sorted-routes.ts |