[
https://issues.apache.org/jira/browse/SLING-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923858#comment-13923858
]
Carsten Ziegeler commented on SLING-3439:
-----------------------------------------
It seems that the problem is that as soon as a custom wrapper object for the
request is involved, parameter handling fails as this is always going back to
the ParameterSupport class which expects the parameters in the query string or
the body of the request.
I think, this needs completely different handling for wrapped requests
> SlingRequestProcessor.processRequest(httpServletRequest, httpServletResponse,
> resourceResolver) no longer passes request params through
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SLING-3439
> URL: https://issues.apache.org/jira/browse/SLING-3439
> Project: Sling
> Issue Type: Bug
> Components: Engine
> Affects Versions: Engine 2.3.0
> Reporter: John Fait
>
> SlingRequestProcessor.processRequest(httpServletRequest, httpServletResponse,
> resourceResolver) no longer passes reqeust params through
> Rendering dependent on request params will no longer render correctly.
> Found in build 2.2.11-R1571320
--
This message was sent by Atlassian JIRA
(v6.2#6252)
