[
https://issues.apache.org/jira/browse/SLING-2156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072304#comment-13072304
]
Antonio Sanso commented on SLING-2156:
--------------------------------------
thinking out loud here, filter or not filter, this would require a change to
the signature of SlingPostServlet#doPost from:
protected void doPost(SlingHttpServletRequest request,
SlingHttpServletResponse response) throws IOException {
to
protected void doPost(SlingHttpServletRequest request,
SlingHttpServletResponse response) throws
ServletException,IOException {
that is compatible with the super class.
Once this is done should be easy (having the behavior configurable) to leverage
the existing error handling mechanism.
> Provide error handling for POST operations
> ------------------------------------------
>
> Key: SLING-2156
> URL: https://issues.apache.org/jira/browse/SLING-2156
> Project: Sling
> Issue Type: New Feature
> Components: Servlets
> Reporter: Antonio Sanso
>
> The error handling mechanism described here [0] doesn't seem to apply also to
> POST operations.
> If an error occurs while posting a resource to repository (e.g.
> avax.jcr.nodetype.ConstraintViolationException: no matching property
> definition found for) the HtmlResponse.html template is rendered.
> This can also represent a security issue since information as
> REFERRER/technology stack are shown.
> IMHO this page should be at least configurable (if the mechanism in [0]
> doesn't suite here).
> [0] http://sling.apache.org/site/errorhandling.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
