[
https://issues.apache.org/jira/browse/THRIFT-813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886133#action_12886133
]
Bryan Duxbury commented on THRIFT-813:
--------------------------------------
bq. Where would I look in order to debug what's going on? What part of the
TJSONProtocol would this be in.
I have no idea - TJSONProtocol.java is a big file, and I didn't write it.
personally, I'd just grep around for any occurrence of the @ sign or something
that indicates URL-encoding is going on.
bq. Also, I've seen several bugs (I think) and I'd like to learn some about the
code base. Are there any ramp up docs for contributors?
Sadly, not really. It's a bit of a jungle in there. The very first thing to do
in every case is to open a JIRA ticket so that we have a record of the bug.
From there, either get out your machete and safari hat and dig in, or try to
find someone who can fix it for you.
> 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.
