Thanks t0m,
I installed your module and it works great - thanks for writing etc.
I guess what I may have been pertaining to is that X-Forwarded-Path
using_frontend_proxy doesn't seem to be implemented although on the
'official'? wiki
I would like to trap every error added to $c-error() and log it, noting the
caller (filename, line number) in the logs.
I've not gotten Catalyst::Plugin::ErrorCatcher to work, so I wrote my own
plugin that overrides $c-error with the following method:
use MRO::Compat;
use
On Thu, Oct 11, 2012 at 5:38 AM, Robert Rothenberg rob...@gmail.com wrote:
I would like to trap every error added to $c-error() and log it, noting
the
caller (filename, line number) in the logs.
I've not gotten Catalyst::Plugin::ErrorCatcher to work, so I wrote my own
plugin that overrides
On Thu, Oct 11, 2012 at 1:38 PM, Robert Rothenberg rob...@gmail.com wrote:
I would like to trap every error added to $c-error() and log it, noting
the
caller (filename, line number) in the logs.
I've not gotten Catalyst::Plugin::ErrorCatcher to work, so I wrote my own
plugin that overrides
On 11/10/12 14:16 Bill Moseley wrote:
On Thu, Oct 11, 2012 at 5:38 AM, Robert Rothenberg rob...@gmail.com
mailto:rob...@gmail.com wrote:
I would like to trap every error added to $c-error() and log it, noting
the
caller (filename, line number) in the logs.
I've not
Hi,
From: John Napiorkowski
Hey All,
I published a blog regarding my thought (and only my thoughts at this point)
regarding how to approach understanding what a long term roadmap for Catalyst
could be. From the recent poll it seems this is a major gap. So here's my way
to kick off a
