Zack Tanner da445e89cd fix: normalize loopback only in hostname (#90158) ...

`NextURL` intentionally canonicalizes loopback hosts (127.x.x.x, [::1],
localhost) to localhost so that internal URL handling is consistent
across equivalent local origins.

However, we were applying a regex replacement to the entire URL before
parsing, which unintentionally rewrote loopback strings inside query
parameter values, eg `?redirect_uri=http%3A%2F%2F127.0.0.1...`. This is
unexpected for anyone that is explicitly passing through different
loopback values.

This fixes it by first parsing the URL with `new URL()`, and then only
apply the replacement logic to `parsed.hostname` when it is a loopback
host. This leaves search unchanged.

Fixes NEXT-4864

2026-02-18 11:54:24 -08:00

..

next-request-node.test.ts

…

next-request.test.ts

…

next-response-cookies.test.ts

…

next-response.test.ts

…

next-server-node.test.ts

…

next-url.test.ts

fix: normalize loopback only in hostname (#90158)

2026-02-18 11:54:24 -08:00

user-agent.test.ts

…