Shannon,
Take a look at this class: ExceptionPassingApplication (lines 200 and down)
https://github.com/tylerwilliams/visualizer2/blob/master/server/visualizer_server.py#L200
You can see an example of wrapping the application handler in a way that
allows you to post-process exceptions and return useful messages to the
client.
Hope this helps,
Aaron
On Tue, Mar 12, 2013 at 4:34 PM, Shannon Cruey <
shannon.cr...@cloudsidekick.com> wrote:
> OK, a year ago I did a workaround for this and am just now revisiting some
> of my uglier code.
>
> I've never been able to figure out how to raise an exception in web.py and
> have it go back to the client as a anything other than an Error 500 -
> "internal server error".
>
> Specifically, I'd like to have the actual details of my exception be
> included in the HTTP Response.
>
> Anyone every figured out how to do this? Is it possible without changing
> the web.py code?
>
> --
> You received this message because you are subscribed to the Google Groups
> "web.py" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to webpy+unsubscr...@googlegroups.com.
> To post to this group, send email to webpy@googlegroups.com.
> Visit this group at http://groups.google.com/group/webpy?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
--
You received this message because you are subscribed to the Google Groups
"web.py" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to webpy+unsubscr...@googlegroups.com.
To post to this group, send email to webpy@googlegroups.com.
Visit this group at http://groups.google.com/group/webpy?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
