There is no builtin way to force a 500 when a 404 is expected, you can achieve that by raising an exception inside the error/document controller when status code is 404. In your case another approach might be to provide default None values to controller parameters (or use **kw), so that instead of raising a 404 it will get into the controller and will complain about invalid values.
I think It should also be possible to write an extension that leverages the _visit method to raise an error when parameters do not match if you want a general solution On Fri, Nov 7, 2014 at 9:58 AM, lebouquetin <[email protected]> wrote: > Le jeudi 6 novembre 2014 05:29:47 UTC+1, Sam Justice a écrit : >> >> After more time debugging than I care to admit, I realized an unexpected >> 404 was being caused by a form handler missing an expected argument. From a >> web server POV this makes perfect sense once I realized what was going on. >> What I'm wondering though is if there's a way to customize this behavior to >> throw an error in a development environment? >> > > I'm interesting in this subject as i also deal with the case sometimes. > > -- > You received this message because you are subscribed to the Google Groups > "TurboGears" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/turbogears. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/turbogears. For more options, visit https://groups.google.com/d/optout.
