AI & Agent Dev Bug Sandbox Back to Radar

Invalid URL When Returning A Relative Location Header In Middleware

Next.js middleware can return a response with a relative Location header (as allowed by HTTP spec), but the internal adapter passes this value directly to the NextURL constructor, which requires an absolute URL, causing an 'Invalid URL' error.

highConfidence 95%Next.js Affected V15.1.0

Origin Analysis

In packages/next/src/server/web/adapter.ts, the Location header from the middleware response is extracted and passed to new NextURL(location) without providing a base URL. NextURL internally calls new URL(location), which throws for relative URLs.

1. Create a Next.js 15.1.0 project with middleware that returns a response containing a relative Location header, e.g., NextResponse.json with headers: { location: '/' } or NextResponse.redirect('/'). 2. Run the dev server and visit a route that triggers the middleware. 3. Observe the error 'Invalid URL' in the terminal or browser.

Fixing Code Block

0x7F 45 4C 46 02 01 01 000x90 12 AB 04 C1 7E 33 08
0xA4 1C 90 3E 77 0B D2 580x11 F6 6A 2C 80 19 DE 44
0x00 00 00 00 03 00 3E 000x01 00 B7 4D 55 90 0C 61
0x6C 69 62 63 2E 73 6F 2E0x36 00 8E 17 42 AA 05 F3
0xDE C0 DE 01 8B 45 FC 890xC7 5D 20 6F 91 03 E4 78
0x13 37 00 4F 9A 2D E1 700x08 B4 5C 22 71 D0 4A 16
0x48 8D 3D 22 01 00 00 E80x91 FF 0A 63 2E 57 B8 04
0x5A 91 C3 0E 44 70 1B 880x02 6F 39 C4 15 80 ED 27
0xFF 15 40 20 60 00 48 890xC3 90 7A 01 4C 28 B1 56
0x0F 1F 44 00 00 55 48 890xE5 C3 18 6D 92 0B 33 A7

Edge Case Audit

While this fix resolves relative URLs, it introduces a dependency on request.nextUrl which may reflect an internal URL behind a reverse proxy, potentially causing incorrect redirect targets if the middleware intends a different origin. Ensure that request.nextUrl correctly represents the external origin. Rollback recommendation: if this fix causes unexpected behavior, revert the change and use absolute URLs in middleware redirects as a temporary workaround.