Unpredictable ResponseAborted message

[ctretyak]

Summary

I got this message only if I open Chrome DevTools and it starts to ask for com.chrome.devtools.json or css source maps. If it is not found, then Next.js answers with 404, but also shows in console ResponseAborted. If I do a separate request to http://localhost:3000/.well-known/appspecific/com.chrome.devtools.json, then Next.js returns 404, but doesn't show ResponseAborted message.
I cannot do minimal reproduction repo, because in fresh project everything is good. May someone bumped into the problem?

Additional information

No response

Example

No response

[GaneshVarma1]

Hey! I’ve seen this before — what you're describing is actually expected behavior when Chrome DevTools makes background requests to look for source maps or .well-known files like:

/.well-known/appspecific/com.chrome.devtools.json

If that file isn’t present (which is totally fine for most apps), Next.js returns a 404. But when DevTools itself aborts the request (which it often does if it detects a 404 early or switches tabs), you’ll sometimes see this:

[ResponseAborted: ]

---

Why it only happens when DevTools is open

• Chrome makes requests to .well-known/... for enhanced debugging info.
• If the resource is missing, Chrome might cancel the request prematurely after initiating it — causing Node.js (or Next.js) to log ResponseAborted, not a "normal" 404.
• If you manually hit the URL in your browser, it’s a full request → 404 → normal behavior.

---

What You Can Do

This message is harmless — you don’t need to handle or suppress it unless it's flooding logs or triggering false alerts.

But if it’s bothering you or showing up in logs you monitor:

1. Add a custom handler for .well-known/* paths in middleware.ts or next.config.js headers to suppress or handle them gracefully.
2. Ignore all .well-known paths in logging tools if you're using structured logs.
3. Optionally serve a dummy file to avoid the request entirely (not usually needed though).

---

Final Thoughts

This isn’t a Next.js bug — it’s just how Chrome DevTools behaves with optional debugging metadata. If your app runs fine otherwise, you can safely ignore the ResponseAborted log.