[
https://issues.jboss.org/browse/WFLY-3385?page=com.atlassian.jira.plugin....
]
Paweł Walczak commented on WFLY-3385:
-------------------------------------
Same problem. Exists also in 8.1.0.CR1. Bellow is my original post to CoderRanch in which
I described the details.
I'm trying to migrate my legacy app to WildFly wildfly-8.1.0.CR2 and I encountered a
problem. The slash character is not decoded when passed as param to the
<jsp:include> tag. The problem can be reduced to following simple code.
In including jsp file:
<jsp:include page="included.jsp">
<jsp:param value="/abc" name="paramName"/>
</jsp:include>
and in included file:
${param.paramName}
This gives the following output in the browser:
%2fabc
instead of /abc. In prevous versions of JBoss AS it worked correctly. I've checked
varous combinations of allow-encoded-slash and decode-url in http connector configuration
but neither of them helped.
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
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.3#6260)