> > I was also a little curious as to why wsgibase was trapping an HTTP > exception at the very end. >
I think the reason it's handled that way is so you can then easily interrupt the normal flow in your app code by raising an HTTP exception yourself (e.g., a model or the controller code can raise an HTTP before the controller returns and gets to the view). In fact, this is how redirect() works (it just raises an HTTP with response code 303). Anthony -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
