[
https://issues.apache.org/jira/browse/SLING-6187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15613238#comment-15613238
]
Alexander Klimetschek edited comment on SLING-6187 at 10/27/16 9:17 PM:
------------------------------------------------------------------------
Could this check be based on the resource type? Then you'd configure the
required post processors based on the RT (or node type), and it's completely
server side.
This lets me think however, that whatever the @suffix triggers in the first
place (say an encryption of a property), which you want to guarantee, should
probably also be defined purely server side.
I.e. if the client forgets/omits the suffix, the requiredPostProcessor check
would not help and you still get an undesired result.
was (Author: alexander.klimetschek):
Could this check be based on the resource type? Then you'd configure the
required post processors based on the RT (or node type), and it's completely
server side.
This lets me think however, that whatever the @suffix triggers in the first
place (say an encryption of a property), which you want to guarantee, should
probably also be defined purely server side.
> Provide a way for a POST request to assert a set of required
> SlingPostProcessors
> --------------------------------------------------------------------------------
>
> Key: SLING-6187
> URL: https://issues.apache.org/jira/browse/SLING-6187
> Project: Sling
> Issue Type: Improvement
> Components: Servlets
> Reporter: Justin Edelson
> Assignee: Justin Edelson
> Fix For: Servlets Post 2.3.16
>
>
> I would like to add support for a new "special" request parameter understood
> by the Sling Post Servlet named {{:requiredPostProcessors}}. This parameter
> may contain a comma-delimited list of names (see below) which *must* be
> available *at the time the request is processed* in order for the request to
> be handled. Whether or not those processors _do_ anything or whether the
> request succeeds or not is a separate question; this is just a preflight
> check if you will.
> If any of the required SlingPostProcessors are not available, the request
> will fail with a 501 error.
> The name of a SlingPostProcessor will be defined by a newly defined service
> registration property {{postProcessor.name}} and default to the simple name
> of the SlingPostProcessor's implementation class if that property is not
> defined.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
