Aaron Freeman wrote:
> Ok, thanks, we will hold off on pushing forward on upgrading until we
> get some idea as to whether this is an issue or not.
>
I checked with the spec and the reference implementation: you're not
supposed to escape content inside a jsp:param. The container is
responsibl
Ok, thanks, we will hold off on pushing forward on upgrading until we
get some idea as to whether this is an issue or not.
Aaron
On 3/31/2010 2:53 PM, Scott Ferguson wrote:
> Aaron Freeman wrote:
>
>> We are experiencing a fundamental change in how data is being passed as
>> a jsp:param bet
Aaron Freeman wrote:
> We are experiencing a fundamental change in how data is being passed as
> a jsp:param between 3.0.22 and 4.0.5. We need to know if this change is
> intentional as it has a work-heavy impact on converting our code base
> over which currently relies on the behavior of 3.0.x
Oh, you will have to swap out the httputil with whatever you use to
URLEncode strings in order to test it.
Thanks,
Aaron
On 3/31/2010 2:46 PM, Aaron Freeman wrote:
We are experiencing a fundamental change in how data is being passed as
a jsp:param between 3.0.22 and 4.0.5. We need to know i
We are experiencing a fundamental change in how data is being passed as
a jsp:param between 3.0.22 and 4.0.5. We need to know if this change is
intentional as it has a work-heavy impact on converting our code base
over which currently relies on the behavior of 3.0.x.
It appears that a call to
