Default Standard Resource

[thescientist13]

As observed in #521 we'll need to make sure we can properly handle a variety of font and image assets. However, what about video or audio formats? Will we have to create standard resources for all of these, or should there be some sort of "default" resource that can try a best effort catch all at the end of the middleware chain.

The thought being that it could try and look at what the browser is expected via Content-Type and just try resolve the file for the user transparently.

[thescientist13]

Thinking about this, I don't this is something we would want, as instead, like we are doing now, we would want to send a 404 response to give proper feedback to avoid "smoothing" over anything. explicit > implicit.