Open edwardsnj opened 7 months ago
My nginx set up is failing to produce 404. So, I am hacking it to give the following message when the file is not found:
That is only good for interactive use. Scripts expect an appropriate HTTP error code. 200 OK is not helpful (even if a user can see with their eyes that it is a bad URL).
When the URL I'm using is no longer good, I expect these urls to return 404 Not Found. Instead it now bounces me to an infinite spinning disk at data.glygen.org. This means that I can't tell that something is wrong, silent fail is bad.