Re: [flask] request.form and 400 Bad Request
- Jon Ribbens
- 2014-08-31 @ 20:58
On Sun, Aug 31, 2014 at 07:45:14PM +0200, Daniel Neuhäuser wrote:
> There is an issue tracker, use it.
> > So could Flask please be changed so that *in debug mode* the unknown
> > key is treated as a normal exception resulting in a traceback?
> +1 on the exception
> -1 on in debug mode, let's do it always
> This breaks backwards compatibility, so if we do so let's make it worth it.
Removing the special-casing in production mode just changes the
response code from 400 to 500, I'm not sure why you would want that.
Removing it in debug mode changes the response from "useless
boilerplate" to "useful debugging info", so the utilitiy is clear.
Plus, changes that only affect debug mode cannot break backwards
compatibility since anyone running production code in debug mode has
bigger problems already.