Hi, On Thu, Sep 20, 2007 at 09:39:05AM -0700, shabda wrote: > Would writing a middleware for this be a good idea? Then if we get the > DNE, we just return 404 from process_exception. And during development > we can just keep our middleware out, so that no real bugs beome 404. > When we deploy, we can just switch this middleware on.
That would work, but I think that you should handle bugs in production explicitly, rather than masking them. If it's a bug, you want to return HTTP 500 (internal server error) and send an e-mail to the server admin notifying him of the problem. Returning a 404 is confusing, and your 404 could be cached (!). 404s should be 404s. There are a variety of ways to turn DNE to 404. Handling DNE->404 explicitly prevents your program from masking a bug. I think that this is a good thing. Does this really save that much code? The negative impact (masking bugs) is significant. -Forest -- Forest Bond http://www.alittletooquiet.net
signature.asc
Description: Digital signature
