Nextjs Prefetch requests handles like ajax request and DT

[Krasav4k1]

Description

In NextJs app routing, newrelic browser engine handle prefetch requests like real request, which is flooding DT and ajax pages

Steps to Reproduce

Expected Behavior

Prefetch request should be ignored, not treat like real request

Relevant Logs / Console output

• Screenshots showing errors
• Page source from the page in question
• HAR file showing New Relic network payloads

Your Environment

• ex: Browser name and version
• ex: Operating System and version
• Browser agent version involved (e.g., v1.229.0)
• APM language and version, if applicable (e.g., Dotnet 10.2.0), and auto|manual

Additional context

[workato-integration]

https://new-relic.atlassian.net/browse/NR-411495

[cwli24]

Hello, do you happen to have a live site or example page + HAR wherein this happens for clarity?

Also, is there a particular reason why you believe they should be ignored by default? (Note that there's an ajax deny list setting if certain requests are not wanted to be captured.)

[Krasav4k1]

Here is the nextjs documentation https://nextjs.org/docs/app/building-your-application/routing/linking-and-navigating#2-prefetching

I cannot add to the ajax deny list those requests, because I need them, but I need real requests not a prefetch requests.

[cwli24]

Right, but prefetch requests shows up as HTTP requests it seems; there's nothing distinguishing them in the browser console, except for certain headers supposedly.

This is definitely not supported at the moment. I'll pass this onto our PM as enhancement request, but do note that the browser agent's official stance is to be framework-agnostic, so this may take some time to green light/get done.