[
https://issues.apache.org/jira/browse/SLING-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13924673#comment-13924673
]
Alexander Klimetschek commented on SLING-3439:
----------------------------------------------
FWIW: Works for me for a different case of the SlingRequestProcessor. Here I
have own implementations of the request and response object that implement the
parts needed by the called servlet (so no wrapped request object). However,
this only uses getQueryString() directly, and none of the getParameter() and
related methods, which would explain why it isn't affected by this issue.
> 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
> Fix For: Engine 2.3.2
>
>
> 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)
