[
https://issues.apache.org/jira/browse/SLING-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13925780#comment-13925780
]
Carsten Ziegeler commented on SLING-3439:
-----------------------------------------
Actually the problem is related to the change in
ParameterSupport.getRequestParameterMapInternal()
While in previous versions this was relying in
getServletRequest().getParameterMap() (for non POST requests), its now relying
on getServletRequest().getQueryString().
> 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)
