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

[earlrobb (Earl)]

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

[system]

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.

Debugging 404 Errors

Sometimes things don’t go as expected when deploying a website. If you see a 404 on your site, that means the page or resource couldn’t be found. There are many possible causes, and the absence of something can be tricky debug if you don’t know where to look. Here are some things you can do to find the cause and fix it. Debugging Tips Check the error code If you see a mostly white screen with 404: NOT_FOUND along with a Code and and ID then you can click the blue info box below the error deta…

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