[jboss-jira] [JBoss JIRA] (WFLY-3385) when using jsp:include the jsp:param being encoded at the included jsp
Zbynek Novak (JIRA)
issues at jboss.org
Sat Jul 26 00:47:31 EDT 2014
[ https://issues.jboss.org/browse/WFLY-3385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988147#comment-12988147 ]
Zbynek Novak commented on WFLY-3385:
------------------------------------
Hi Stuart,
I have found out, that the problem with merging of URL encoded query parameters still exists.
When you forward request processing to path with query parameter, that do not contain special characters only spaces (see bellow), then QueryParametersUtil parseQueryString do not trigger decode of parameter value.
This key remains encoded:
&description=very+long+message
Can you check it?
Thanks
ZZ
> when using jsp:include the jsp:param being encoded at the included jsp
> ----------------------------------------------------------------------
>
> Key: WFLY-3385
> URL: https://issues.jboss.org/browse/WFLY-3385
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Affects Versions: 8.1.0.CR2
> Reporter: roy mizrachi
> Assignee: Stuart Douglas
> Fix For: 9.0.0.Beta1
>
>
> I have JSP A that includes JSP B like this:
> <jsp:include page="../anotherFolder/B.jsp">
> <jsp:param name="pathToRootContext" value='../' />
> </jsp:include>
> In JSP B i have the following:
> String pathToRootContext = request.getParameter("pathToRootContext");
> The value i get in the pathToRootContext is "..%2f"
> I tried the following but it didn't help:
> <servlet-container name="default" default-encoding="UTF-8">
> <jsp-config development="true" java-encoding="UTF-8"/>
> </servlet-container>
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
More information about the jboss-jira
mailing list