FileMiddleware and 404 responses #592
Description
Currently the FileMiddleware runs whenever the router throws a 404 HTTPError. It does not run if a Response is returned whose status is 404.
Should we consider a returned 404 responses as a reason to kick off the FileMiddleware? On one hand a returned response could be considered as already handled and therefore we shouldn't kick off the FileMiddleware. On the other people have been caught out by this.
Options:
- Treat 404 responses the same as errors.
- Add an option to treat 404 responses the same as errors.
- Improve documentation.