If you’re like me, HTTP status code
200 Object] unknown probably doesn’t ring any bells. Of course, that’s mainly because it doesn’t exist.
So, how did I end up with the screenshot above? I’ve been running with scissors again. It was one of the more popular web frameworks for Node.js that I cut myself with this time: Express.js
Unfortunately, a malformed status code like
200 Object] will cause some browsers (including the version of Chrome I was using at the time) to refuse loading the page at all. That quickly elevated the importance of my strange status code from a trivial oddity to an annoying thorn in the side.
As it turns out, my code was running up against a documented Express feature and the remedy was simple enough.