[
https://issues.apache.org/jira/browse/SLING-6187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15746788#comment-15746788
]
Alexander Klimetschek commented on SLING-6187:
----------------------------------------------
What about this alternative?
- these encrypted properties are prefixed with a value like j_ so they do not
get handled by the normal SlingPostProcessor (or another prefix, configurable
as per
https://sling.apache.org/documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.html#omitting-some-parameters
)
- that post processor in question only handles the ones with prefix to be sure
they don't get written without it and throws an error otherwise (forces clients
to change the request, alternatively a warning)
- some new mechanism needs to be added to make the reuqest fail if these
properties were not processed so the original request can fail if that post
processor is offline
IMO this needs to be solved on the interface layer (i.e. the request parameters
etc.), and not be depending on the implementation (who knows, maybe we turn
such a post processor into a core feature at some point).
> 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
>
> Attachments: SLING-6187-profile.diff, SLING-6187.patch
>
>
> 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)
