imbo/imbo — pull request #95 by rexxars (2012-10-29 14:35:54+00:00)
Title: Errors on an image resource with explicit content type provided fails to render

This fix simply uses the default mime type response writer if the explicit file type used does not have an associated response writer.

On the image resource, it makes more sense this way, as providing a .jpg or .png format is common, and it makes debugging easier to actually see the error message generated when something goes wrong (incorrect access token, for example).

On resources other than an image, it might make more sense to throw a 406 to let the user know that the explicit content type provided does not have an associated formatter.

Not sure if there is a more optimal solution to the problem - feel free to reject if a better solution is found.