2

I have some JSON which is perfect when tested with jsonlint, but gives an Invalid character error when i try to parse it to an object. I've looked at the JSON string and it seems ok. How do I see funny characters that may be hidden??

here is the js fiddle link. http://jsfiddle.net/UexKp/

Paul Sweatte
  • 24,148
  • 7
  • 127
  • 265
Hubert Boma Manilla
  • 128
  • 2
  • 9

3 Answers3

1

This may not be the problem you're encountering exactly, but I fixed a similar error in the JSON being returned by my ajax calls (in Internet Explorer only, of course) by specifying that the response type should be interpreted as json, not text. Since I'm using jQuery, this entailed setting the dataType param in the ajax options to "text json", which converts the response appropriately from text (as IE sees it) to JSON.

If this won't work for you, you could also try altering the response type coming from the server directly, assuming you have access to it, so that it correctly reports that the response coming back is JSON, not text.

brandwaffle
  • 1,252
  • 9
  • 11
0

You could use a debugging proxy like Fiddler (http://www.fiddler2.com/fiddler2/) and then inspect the raw data of the JSON-Request to see if there are some unwanted characters in the response.

Michael Sandino
  • 1,818
  • 1
  • 13
  • 10
0

Nothing wrong with the JSON: http://jsfiddle.net/UexKp/2/

The { and } are not treated as object literal when they can be treated as block, so having a variable assignment for example fixes it. You could also wrap it with ( and ) as shown in fiddle /1

Esailija
  • 138,174
  • 23
  • 272
  • 326
  • I think what he gets is JSON, not a JS-Object. And that's just a string that is parsed into a JS-object with tools like JSON.parse() – Michael Sandino Apr 13 '12 at 10:41
  • @MichaelSandino Then he should paste whatever he is getting... There is nothing else to work with but the jsfiddle which works just fine after making it an expression. – Esailija Apr 13 '12 at 10:44