You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by bu...@apache.org on 2003/09/22 21:07:49 UTC
DO NOT REPLY [Bug 23283] -
WebServiceProxy doesn't re-encode request parameters
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23283>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23283
WebServiceProxy doesn't re-encode request parameters
tcollen@neuagency.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
------- Additional Comments From tcollen@neuagency.com 2003-09-22 19:07 -------
Not actually a bug in the WSProxy, you need to use the
RawRequestParameterInputModule in order to pass encoded request params to the
remote service.
For the request "http://foo.com/service?actor=johnny+depp":
{request-param:actor} is equal to the string "johnny depp"
{raw-request-param:actor} is equal to the string "johnny+depp"
Something in the docs should reflect how to do this correctly.
Re: DO NOT REPLY [Bug 23283] - WebServiceProxy doesn't re-encode
request parameters
Posted by Tony Collen <co...@umn.edu>.
Geoff Howard wrote:
<snip/>
> Does the sample even mention this input module?
I don't think so, I ended up finding the module on my own after wondering if there was a module to
URL encode a string. (which might still be useful).
IMHO I wouldn't mind a simpler example of the wsproxy, since it's not totally apparent that it
automatically passes request parameters to the remote service.
I'll make some notes on the wiki pages for the input modules as well as the wsproxy about this, and
I'll be sure to mention this usage of the raw-request-param module in my upcoming inputmodules docs.
> Geoff
>
Tony
Re: DO NOT REPLY [Bug 23283] - WebServiceProxy doesn't re-encode
request parameters
Posted by Geoff Howard <co...@leverageweb.com>.
bugzilla@apache.org wrote:
> DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
> RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
> <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23283>.
> ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
> INSERTED IN THE BUG DATABASE.
>
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23283
>
> WebServiceProxy doesn't re-encode request parameters
>
> tcollen@neuagency.com changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Status|UNCONFIRMED |RESOLVED
> Resolution| |INVALID
>
>
>
> ------- Additional Comments From tcollen@neuagency.com 2003-09-22 19:07 -------
> Not actually a bug in the WSProxy, you need to use the
> RawRequestParameterInputModule in order to pass encoded request params to the
> remote service.
>
> For the request "http://foo.com/service?actor=johnny+depp":
>
> {request-param:actor} is equal to the string "johnny depp"
> {raw-request-param:actor} is equal to the string "johnny+depp"
>
> Something in the docs should reflect how to do this correctly.
Does the sample even mention this input module?
Geoff