Bug (and workaround): 404 page returns HTTP 200

Welp… turns out I can’t even try @hrishikesh’s idea because I have to run builds locally and because Netlify CLI doesn’t work on my machine, which prevents me from deploying edge functions on my site.

Again, I really wish for a proper solution here…

We’re going in circles at this point. The current behaviour is expected and not set to change unless someone can point to a RFC that states otherwise.