[
https://issues.apache.org/jira/browse/AXIS2-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12555653#action_12555653
]
David Hancock commented on AXIS2-3405:
--------------------------------------
Hi Keith,
Thanks for the quick reply.
I'm not sure I understand you though.
The problem it that if I make a servlet request which has a parameter with a
value that includes an ampersand, then I need to encode that ampersand as %26.
That's fine, it works in Tomcat and SunAppServer exactly as expected.
But if I pass the same request through Axis2, it decodes the %26 to an
ampersand before it parses the parameters from the query portion of the URL.
I know next to nothing about WSDL and POJO deployment and the REST of it (ha
ha), but it seems to me that wen Axis2 is operating in REST mode, it has full
control over how it maps inbound URLs to the classes that it is providing web
services for. Therefore if this mapping is breaking, then Axis2 might be the
place to look for a fix.
Or have I got completely the wrong end of the stick?
regards,
Dave Hancock.
> Encoded ampersands in REST URLs terminate parameters
> ----------------------------------------------------
>
> Key: AXIS2-3405
> URL: https://issues.apache.org/jira/browse/AXIS2-3405
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.2
> Reporter: Sean Hile
> Assignee: Keith Godwin Chapman
>
> My project uses Axis2 to provide a REST interface. If, in the URL, there is
> an encoded ampersand for one of the parameter values, the parameter value is
> truncated at the encoded ampersand. For example:
> http://example.com/myService?param=Foo%20%26%20Bar
> The param value should be "Foo & Bar" but it is truncated to "Foo ".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
