[
https://issues.apache.org/jira/browse/THRIFT-813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886168#action_12886168
]
T Jake Luciani commented on THRIFT-813:
---------------------------------------
Hi Jordan,
This too is most a browser side encoding issue. The js implementation of
writeString uses encodeURIComponent()
I suppose this isn't consistent, with the non javascript protocol readers. but
the js readString uses decodeURIComponent()
We could implement our own encoder to encode only JSON special chars.
-Jake
> Getting URL encoded strings back on the server side for example: ("@" becomes
> "%40")
> -------------------------------------------------------------------------------------
>
> Key: THRIFT-813
> URL: https://issues.apache.org/jira/browse/THRIFT-813
> Project: Thrift
> Issue Type: Bug
> Affects Versions: 0.4
> Environment: Linux server, web based js thrift client
> Reporter: Jordan
>
> Hello,
> Please help me understand what is going on.
> I'm using the js client for thrift and making calls to a java-bean thrift
> server. In the server implementation, I examine the strings that are passed
> through a service call, and they are URL encoded. For example.
> [email protected] would be hi%40bye.com
> Where is this happening. I'm guessing it's at the TJSONProtocol. I expect
> many characters to be percent escaped like this as it's coming across the
> wire, but once it gets to the server code it should be back in plain ol'
> string land.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
