redirects in nextConfig do not log out when successfully redirected

### Link to the code that reproduces this issue https://codesandbox.io/p/devbox/still-microservice-h6wdrp ### To Reproduce 1. Add a redirect (i.e.: one that redirects to another domain that is not serviced by the hosting app) 2. Start the Next.js server 3. Trigger the redirect Sample redirect: ```js { source: "/:path*", destination: "http://www.nextjsrocks.com/:path*", permanent: true, has: [ { type: "host", value: "nextjsrocks\\.com(:\\d+)?", }, ], } ``` Sample curl to trigger: ```sh curl -I --connect-to nextjsrocks.com:3000:localhost http://nextjsrocks.com:3000/asdf ``` ### Current vs. Expected behavior I would expect a log to appear in the console output as a redirect to acknowledge that Next.js recognized the request and issued a redirect. ### Provide environment information ```bash Operating System: Platform: linux Arch: x64 Version: #1 SMP PREEMPT_DYNAMIC Sun Aug 6 20:05:33 UTC 2023 Available memory (MB): 4102 Available CPU cores: 2 Binaries: Node: 20.9.0 npm: 9.8.1 Yarn: 1.22.19 pnpm: 8.10.2 Relevant Packages: next: 15.5.1-canary.24 // Latest available version is detected (15.5.1-canary.24). eslint-config-next: N/A react: 19.1.1 react-dom: 19.1.1 typescript: 5.3.3 Next.js Config: output: N/A ``` ### Which area(s) are affected? (Select all that apply) Output, Redirects ### Which stage(s) are affected? (Select all that apply) next dev (local), Other (Deployed), next start (local) ### Additional context _No response_