[
https://issues.apache.org/jira/browse/SLING-2156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13563816#comment-13563816
]
Antonio Sanso commented on SLING-2156:
--------------------------------------
trying to restore an old topic I'd be inclined to apply the last patch [0]
(with some additional integration tests...)
This patch in [0] "leverages" SLING-2223 that "offers" a great framework to
solve this "problem" in a really not invasive way...
Shouldn't we want to put this in the servlet post bundle we can even ship a
separate bundle as shown in [1].
WDYT?
[0]
https://issues.apache.org/jira/secure/attachment/12505883/SLING-2156-patch.txt
[1]
https://issues.apache.org/jira/secure/attachment/12505884/post_error_handling
> 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
> Assignee: Antonio Sanso
> Attachments: post_error_handling, SLING-2156-patch.txt,
> SLING-2156-patch.txt, SLING-2156-patch.txt, SLING-2156-patch.txt
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
