I would also add that this choice is wise, because showing such internal info to the end user in a production environment is likely to be frown during a security audit.

Of course this is a general statement that does not take into account what Stephen might have read about how RESTful apps should respond to errors, but I would be surprised of the contrary.

Cheers,

    Flavio.


On Thu, Jul 7, 2011 at 1:44 PM, Takeshi OKURA <okura3@gmail.com> wrote:
Hi Stephen.

2011/7/7 Stephen Fenwick-Paul <stephen@activeg.org>:
> With the environment set to development, each of these responds as I expect.
> Case 1 gives me a full backtrace, case 2 gives me a a json with just the
> error message, and case 3 again give me a full backtrace,
> Now moving to the production environment. I get
(snip)
> Which is OK, but where is the meaningful message to the user gone?

To show the stack trace, show_errors variable in a
environment/production.yml shuld be 1. I think so.

It's 1 in development.yml. But in production.yml It's 0.

best regards.

--
Takeshi OKURA
_______________________________________________
Dancer-users mailing list
Dancer-users@perldancer.org
http://www.backup-manager.org/cgi-bin/listinfo/dancer-users