Mike

@kenjones-cisco I think the best (only?) way to solve this for all scenarios is to allow route middleware to run before validation. That then allows us to process any request...

Fair point. If those libs format `req.files` in a standard way then it would make sense. Looks like your pull request references `req.file` though. Is that standard? If there is...

Looking at the [swagger spec](https://github.com/swagger-api/swagger-spec/blob/master/versions/2.0.md#items-object) it looks like you can't have an array of files as a parameter so single file support may well be enough? I guess the fallback...

Oops I guess you can have multiple params that are each a file. In that case you would have an array of files and you'd need to scan them to...

See third paragraph from bug report. Here's the quote from the link there. "If you chain multiple middleware together, you will find out, that express uses streams, but this does...

It sounds like it could arise with any middleware which tries to catch all stream events. Not sure how common that is. As mentioned, multer is from the express team...

Hey @lgomez, 1. Do you mean remove a full swagger api version you've previously registered? Not currently, could you outline your use-case there? 2. You can pass a yaml or...

Thanks for the details. That's an approach I'd not considered. In regards to removing all routes of an API, I may look at adding this when I get a little...

@JamesSkinner Thanks for digging this one out, good find. What if we move the exception catching to only target the direct middleware. ```javascript function authorize(req, res, next) { return Promise.all(...)...