The issue was fixed by encoding the JSON with URL.encodeComponent().

I'm very thankful for your help!

On May 15, 10:12 pm, Thomas Broyer <t.bro...@gmail.com> wrote:
> On 15 mai, 22:14, Hannson <hann...@gmail.com> wrote:
>
> > I think I was wrong.
>
> > This problem does not happen unless the json string contains quotes
> > (escaped automatically by GWT like this: "this is a string that
> > contains \"quotes\"" ), even when URL.encoded. I'm not sure if this is
> > a GWT or Django issue.
>
> > Does anyone have any ideas?
>
> Have you tried URL.encodeComponent() on your JSON before sendRequest
> ("json=" + json, ...) ?
>
> I believe GWT is right on both JSON serialization and
> URL.encodeComponent() (this one is deferred to the browser);
> RequestBuilder is OK too (and let's hope your browser's XMLHttpRequest
> too).
> So I'd say that either your code is buggy, or PHP, or Django (PHP
> being buggy in many ways isn't a scoop). You should first have a look
> at the request's content that goes on the wire (use Firebug or a
> similar tool, or Fiddler or similar network "debugger"), and if it
> looks OK, then the problem is on the server side.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to