Comment 5 for bug 1177623

The core issue described by the bug is one of user experience, so I think the direction is certainly valid. The response should still be a 500, as well. However, we're not providing adequate feedback to the deployer about what went wrong, and perhaps providing too much information to the API user (who *may* not be the deployer).