Comment 2 for bug 1406025

Dan Scott (denials) wrote :

Added a second commit to the branch which does the dance described at of setting the status to the error code, then resetting the apache status to OK so that the HTML can be generated as before, rather than the ugly default server error page. The HTTP header still shows the 404 or 410 as desired, so that machines can do the right thing.

We do this only for the known cases of HTTP_NOT_FOUND and HTTP_GONE for records; these status codes are otherwise not thrown by our application.