I have a very simple site that I am using to advance my knowledge of next.js. I am looking at Observability:Edge Request to make sure my firewall is blocking php and security vectors like .git . I have been keeping up with next.js updates because of recent security CVE’s I have been seeing. Somewhere in the recent updates I started noticing routes like /index.segments/PAGE.segment. Is this someone trying to exploit a vulnerability or is it normal to see routes like this in next.js 6.1.1. The site is static with the most advanced functionality being a form that generates an email.
The current behavior in Observability is routes showing up as:
/index.segments/PAGE.segment
/index.segments/_tree.segment
/index.segments/_head.segment
/index.segments/@modal/DEFAULT.segment
Expected behavior is that Observability:Edge Requests would only show routes that browsers would follow ie. myfolder/mypage/
All of these odd routes show up as between 50% and 100% Cached so I am hoping they are system files and not some sort of attack or a misconfiguration on my part.
NPM outdated shows all packages up to date except tailwind and flowbite. I have not had an opportunity to update those yet.