Top Paths logs contain .well-known/resource-that-should-not-exist

Help
1

While checking Usage → Top Paths I found the following in the logs:

myUrl/.well-known/resource-that-should-not-exist-whose-status-code-should-not-be-200/

I have seen this 2 times over as many months. Should I be seeing these in my Top Paths? If I go to directly to the URL in my browser I can see in my developer tools that the status of that path is 404.

My /.well-known directory contains:

gpc.json 
security.txt
traffic-advice

In next.config.js I have:

    async headers() {
      return [
        {
          // config for Chrome Privacy Preserving Prefetch Proxy
          source: '/.well-known/traffic-advice',
          headers: [{ key: 'Content-Type', value: 'application/trafficadvice+json' }],
        },

Can someone give me some guidance on why I am seeing this and if or how I should fix it? I know its suppose to return 404 but I can’t tell if its a bot doing its or some problem with my code/setup.

thx,
Earl

2

There’s another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes.

A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.