Response from patched fetch has undefined url property

[adamjmcgrath]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.5.0: Mon Apr 24 20:53:19 PDT 2023; root:xnu-8796.121.2~5/RELEASE_ARM64_T6020
    Binaries:
      Node: 18.16.0
      npm: 9.5.1
      Yarn: 1.22.19
      pnpm: 8.6.0
    Relevant packages:
      next: 13.4.7
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: N/A

Which area(s) of Next.js are affected? (leave empty if unsure)

App directory (appDir: true)

Link to the code that reproduces this issue or a replay of the bug

adamjmcgrath/next-res-url@6e7c9e8

To Reproduce

• npm run dev
• Visit localhost:3000
• Observe the logs in the console:

res.url with defaults: 
res.url with "no-store": https://dog.ceo/api/breeds/list/all

Describe the Bug

When you make a fetch from an app directory page, the response does not have a URL property.

This causes libraries like oauth4webapi, to throw Invalid URL errors when they process fetch responses.

If you force the fetch not to cache, using cache: no-store the response has a URL - so it's probably an issue with https://github.com/vercel/next.js/blob/v13.4.7/packages/next/src/server/lib/patch-fetch.ts

Expected Behavior

The response from fetch should always have a url property equal to the final URL obtained after any redirects. https://developer.mozilla.org/en-US/docs/Web/API/Response/url

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

Only tested in development mode

[github-actions]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.