Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
0.4
-
None
-
None
-
Linux server, web based js thrift client
Description
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.
hi@bye.com 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.
Attachments
Issue Links
- is cloned by
-
THRIFT-885 Url encoded strings never get decoded? How do we fix this?
- Closed