Comment 9 for bug 1153926

Changing a 200 to a 404 is an explicit no-no according to the api stability policy. Is this issue, which I presume is a longstanding one, really serious enough to violate that policy in a soon-to-be-deprecated api?