A signficant amount of Console `GET` failures for page-data.json requests

[zstix]

Steps to reproduce

NOTE This error happens intermittently on different pages It seems to be triggered when a user traverses the navigation

• Go to https://docs.newrelic.com/docs/telemetry-data-platform/ingest-manage-data/understand-data/new-relic-data-types/
• click on Query your Data in the right nave
• and review the console
• See the errors for page-data.json

Go to

• go to https://docs.newrelic.com/docs/agents/php-agent/getting-started/introduction-new-relic-php/
• click on New Relic for PHP in the right nav
• • See the errors for page-data.json

Tell us what you need

When I scroll down the page on the "Introduction to New Relic for PHP" page, I see the following errors in my console:

It's worth noting that this page gets a lot of traffic and causes a significant amount of errors.

Doc information (don't delete this section)

• https://docs.newrelic.com/docs/agents/php-agent/getting-started/introduction-new-relic-php/
• OS: MacOS
• Browser: Chrome 90
• Device: MacBook Pro

[zstix]

@jpvajda Here's another one that's causing a lot of issues.

[roadlittledawn]

FWIW: i see this error on most pages on the site

[roadlittledawn]

Some potentially useful info in this thread: gatsbyjs/gatsby#16097

[zstix]

We decided to timebox an hour to look into this (and reach out to Gatsby about it). If this takes longer than that, we should re-estimate it and prioritize it for a later sprint.

[roadlittledawn]

So far, it looks like this is expected behavior for Gatsby's pre-fetching page data for any links on a given page (was added as a performance improvement to avoid a monolithic page manifest file on large sites).

and so far it appears that 404s occur for links that are redirected to other pages. which would make sense that there's no page data for a given path that doesn't actually have content and instead redirects to one that does.

you'll notice that these errors don't occur on the What's New landing page. we don't have any redirected links on this page, so prefetching calls don't 404.

[jpvajda]

This is seems to be happening on all or most pages... so do we need to actually create files for page-data.json requests?

Now, when a page navigation occurs, Gatsby makes a request directly to the server for the page-data.json, instead of checking the global manifest (which doesn't exist anymore).

[roadlittledawn]

This is seems to be happening on all or most pages... so do we need to actually create files for page-data.json requests?

Now, when a page navigation occurs, Gatsby makes a request directly to the server for the page-data.json, instead of checking the global manifest (which doesn't exist anymore).

no, that's internal to how Gatsby does its thang