Jeremy Whitlock

I had to reopen this since it broke backward compatibility. I will add this back when `1.0.0` is released.

This will not be released prior to `1.0.0`, which itself might not be released due to this project being effectively deprecated, see #335.

Can you elaborate? Swagger should allow for some level of dynamic even if it's just having an open schema for the dynamic part(s).

The idea behind this was that if the requested path is not one defined in your Swagger document, it's a no-op as far as this middleware is concerned. I like...

Throw in some middleware after the `swagger-tools` middleware that will treat anything it gets as an error.

Yeah, I don't think this was intentional.

Sorry for the long delay _(holidays)_.

I'm not completely opposed to this. I wonder what @fehguy or @webron have to say about this.

That's my stance as well. If you say you consume `application/json` but fail to set `Content-Type` to `application/json`, that's on you. But with that being said, I'm not against updating...

What I meant by _abused_ is if someone wanted to be malicious, all they'd have to do is send `Content-Length: 0` and all validation is disabled but that does not...