Currently werkzeug 1.5.1 (similar to previous versions), by default does not raise multipart form posting errors. This is the same behavior as before (albeit with a bugfix), but I strongly feel that by default werkzeug should raise exceptions on form parsing. See my comments on this ticket (which I've reopened with a lower priority):
http://dev.pocoo.org/projects/werkzeug/ticket/394#comment:2 """ I'm still a little concerned about the default behavior on form parsing failures in werkzeug.wrappers.Request being to do nothing. This is of course debatable, but I feel that exploding (vs. NOOPing) is a more a reasonable default behavior - otherwise your application could behave strangely working on partial information in POST. I can imagine very bad scenarios where you loose an optional field which play a critical business role - e.g. an email opt-out flag in a user registration form - and this leads to problems that become very difficult to debug downstream. I like having an overridable method _form_parsing_failed() - but why not make the default implementation raise the error instead of doing nothing? """ Am I alone in this opinion? Armin and other werkzeug devs -- Is the current behavior born out of concern for preserving backwards compatibility or do you think the silencing the error is really the best behavior? If the latter, why? I'd appreciate any feedback. Thanks, Drew --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pocoo-libs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pocoo-libs?hl=en -~----------~----~----~----~------~----~------~--~---
