You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Alexander Klimetschek (JIRA)" <ji...@apache.org> on 2008/09/29 13:46:44 UTC

[jira] Closed: (SLING-669) SlingPostServlet swallows exceptions

     [ https://issues.apache.org/jira/browse/SLING-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander Klimetschek closed SLING-669.
---------------------------------------


> SlingPostServlet swallows exceptions
> ------------------------------------
>
>                 Key: SLING-669
>                 URL: https://issues.apache.org/jira/browse/SLING-669
>             Project: Sling
>          Issue Type: Improvement
>          Components: Servlets Post
>    Affects Versions: Servlets Post 2.0.2
>            Reporter: Alexander Klimetschek
>            Assignee: Felix Meschberger
>            Priority: Minor
>             Fix For: Servlets Post 2.0.4
>
>         Attachments: SLING-669.patch
>
>
> The SlingPostServlet handle Exceptions/Throwables by just setting the error to the o.a.s.api.servlets.HtmlResponse, which in the standard implementation only prints error.toString() as the message title, which omits the stacktrace.
> The servlet should at least log the error in DEBUG level. Additionaly, one might want to extend the HtmlResponse to include the full stacktrace in case of an error (the html response output is intended for developers, so it could include all kinds of nasty error messages ;-))

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.