Exceptions raised during request processing will not always be caught and returned as a 500 error

[coddingtonbear]

An error report was received from @kaiiiz in #23:

I notice a related issue, for the PUT /vault/{filename} endpoint, if the specified folder in the path doesn't exist, the server will hang forever. (e.g. filename = c/d.md and folder c doesn't exist)

What I expected to get from the server response:

It should return 405 Bad Request or create the nested folder structure before creating the new file (maybe an optional parameter for this functionality?).

Originally posted by @kaiiiz in #23 (comment)

[coddingtonbear]

This was fixed (in that requests can no longer hang and will return a 500 error for unhandled errors) via 1f67f2c.