ripple-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brent Lintner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (RIPPLE-49) Ripple cuts json sent by POST
Date Thu, 09 Jan 2014 21:21:50 GMT

    [ https://issues.apache.org/jira/browse/RIPPLE-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867077#comment-13867077
] 

Brent Lintner commented on RIPPLE-49:
-------------------------------------

Hey Pau,

No clues (and I have not seen this before).. but it *does* seem like a bug.

Can you tell me where the JSON request is going to (the URL of the proxy)? I wonder, as it
seems you are using BlackBerry's version, and I do not know what has been done to it since
Ripple was brought into the ASF, or if they are even using the same Proxy code.

Have you tried this with the most recent version shipped via NPM (https://npmjs.org/package/ripple-emulator),
where you can use a local Proxy instance (if you want)? The Chrome Store and BlackBerry distributions
are either outdated, or unsupported in this community (although we wil try to help if possible!).
:-s

If it is still an issue, please let us know, and (ideally with some steps to reproduce) it
can be squashed. :-)

> Ripple cuts json sent by POST
> -----------------------------
>
>                 Key: RIPPLE-49
>                 URL: https://issues.apache.org/jira/browse/RIPPLE-49
>             Project: Apache Ripple
>          Issue Type: Question
>         Environment: It happens in both Win and MAC. 
> Ripple Emulator (Beta)
> Ripple UI (vundefined)
> Ripple Build & Deploy (v0.9.5)
>            Reporter: Pau Bartrina
>              Labels: forwarding, json, parameterhandler, port, post_method
>
> Everytime I send a well formatted json through Ripple, the PHP on the server side receives
a truncated version of the same one. I print on console the string the very moment before
sending and I echo what the PHP receives. No matter de length, the PHP always receive a percentage
less of information. 
> Let me make it clear.
> I send something like: "data="+JSON.stringify(xdata);
> where xdata is: {user : "user", key : "asdfghjkl"};
> The PHP on the server side always gets: data = {user:"user", key:"asdfg
> The very same POST_method works perfectly on a website without using ripple.
> Any clues on this?



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message