Prefixing the JSON string in this manner is used to help prevent JSON
Hijacking. The prefix renders the string syntactically invalid as a script
so that it cannot be hijacked. However firebug does not seem to be able to
evaluate it as JSON neither because firebug isn't creating the JSON tab for
these kind of responses. Is this a bug, a feature or a defect?
Would it be possible that when the returned JSON has {}&& prefix it would
work the same way like it doesn't have it, just cutting it out?
--
You received this message because you are subscribed to the Google Groups
"Firebug" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/firebug.
To view this discussion on the web visit
https://groups.google.com/d/msgid/firebug/cfc37520-b1a6-4dc2-b2ed-206ad7304bcb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
