infrae.wsgi questions

--===============3864275903540140207==
Content-Type: multipart/alternative; boundary=000e0cd358fe15552f04ad74be2b

--000e0cd358fe15552f04ad74be2b
Content-Type: text/plain; charset=ISO-8859-1

Hi Devs,

Bethel has added a few exceptions to our Silva which are cropping up in the
new wsgi error log quite a bit -- they're drowning out the real errors.

It is possible to manually add ignored exceptions, by viewing the error log
and using the form at the bottom.

I was wondering if it is possible to permanently add ignored exceptions?
 For instance by using a product-config section in zope.conf or something?

I also miss some of the extra reporting the Zope 2 error log object provided
-- like full inspection of the request object's form, other, lazy and env.
 Could that be added to the error log?  Or is there some way to log to the
zope 2 error log from infrae.wsgi?

When rendering a code source, and the source raises an exception,
SilvaExternalSources catches that exception.  It logs it to the Zope2
error_log.  Now we have two logs to look at per zope node.  Is it possible
to either:
1) have any error logged to the zope2 error_log also go to the infrae.wsgi
error log?
2) log caught exceptions to the infrae.wsgi error log?

Thanks,
Andy

--000e0cd358fe15552f04ad74be2b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Devs,<div><br></div><div>Bethel has added a few exceptions to our Silva =
which are cropping up in the new wsgi error log quite a bit -- they&#39;re =
drowning out the real errors.</div><div><br></div><div>It is possible to ma=
nually add ignored exceptions, by viewing the error log and using the form =
at the bottom.</div>
<div><br></div><div>I was wondering if it is possible to permanently add ig=
nored exceptions? =A0For instance by using a product-config section in zope=
.conf or something?</div><div><br></div><div>I also miss some of the extra =
reporting the Zope 2 error log object provided -- like full inspection of t=
he request object&#39;s form, other, lazy and env. =A0Could that be added t=
o the error log? =A0Or is there some way to log to the zope 2 error log fro=
m infrae.wsgi?</div>
<div><br></div><div>When rendering a code source, and the source raises an =
exception, SilvaExternalSources catches that exception. =A0It logs it to th=
e Zope2 error_log. =A0Now we have two logs to look at per zope node. =A0Is =
it possible to either:</div>
<div>1) have any error logged to the zope2 error_log also go to the infrae.=
wsgi error log?</div><div>2) log caught exceptions to the infrae.wsgi error=
 log?</div><div><br></div><div>Thanks,</div><div>Andy</div>

--000e0cd358fe15552f04ad74be2b--

--===============3864275903540140207==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
silva-dev mailing list
silva-dev-IAPFreCvJWM6s/[email protected]
https://lists.infrae.com/mailman/listinfo/silva-dev

--===============3864275903540140207==--