RailsCasts Pro episodes are now free!
Learn more or hide this
GitHub User: Flambino
Yeah, web APIs are (or should be) sticklers for proper status codes, but any ol' HTML browser can infer a lot from the status code too. Whether or not to use the URL when auto-completing an address for the user, for instance. It's annoying to have the browser remember a URL for an error page, only because that page accidentally sent a 200 OK
Nice episode, but it would be beneficial to add something like response.status = request.path[1..-1] to make the status code carry over (if anyone knows of a nicer way to do this, speak up).
response.status = request.path[1..-1]
Otherwise, the error pages will all have a status of 200 OK since the error controller itself responded normally.