fix: Update URL resolution logic to handle search parameters on root path /?foo=bar

packages/next/src/lib/metadata/resolvers/resolve-url.test.ts

@@ -62,6 +62,12 @@ describe('resolveAbsoluteUrlWithPathname', () => {
         'https://example.com/foo'
       )
     })
+
+    it('should resolve absolute internal url with query', () => {
+      expect(resolver('https://example.com/?foo=bar')).toBe(
+        'https://example.com/?foo=bar'
+      )
+    })
   })
 
   describe('trailingSlash is true', () => {
@@ -102,13 +108,20 @@ describe('resolveAbsoluteUrlWithPathname', () => {
       expect(resolver(new URL('https://example.com/foo?bar'))).toBe(
         'https://example.com/foo?bar'
       )
+      expect(resolver('https://example.com/?foo=bar')).toBe(
+        'https://example.com/?foo=bar'
+      )
     })
 
     it('should not add trailing slash to relative url with query', () => {
       expect(resolver('/foo?bar')).toBe('https://example.com/foo?bar')
       expect(resolver(new URL('/foo?bar', metadataBase))).toBe(
         'https://example.com/foo?bar'
       )
+      expect(resolver('/?foo=bar')).toBe('https://example.com/?foo=bar')
+      expect(resolver(new URL('/?foo=bar', metadataBase))).toBe(
+        'https://example.com/?foo=bar'
+      )
     })
 
     it('should not add trailing slash to relative url that matches file pattern', () => {

packages/next/src/lib/metadata/resolvers/resolve-url.ts

@@ -110,7 +110,10 @@ function resolveAbsoluteUrlWithPathname(
   if (typeof result === 'string') {
     resolvedUrl = result
   } else {
-    resolvedUrl = result.pathname === '/' ? result.origin : result.href
+    resolvedUrl =
+      result.pathname === '/' && result.searchParams.size === 0
+        ? result.origin
+        : result.href
   }
 
   // Add trailing slash if it's enabled for urls matches the condition