You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 2, 2022. It is now read-only.
We are using a prefix before sending back the JSON responses in our API like in the example below:
)]}',
{"data": "wow"}
note that the above prefix is in fact ")]}',\n" but sometimes the white spaces are stripped out and it's only ")]}',"
"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."
This prefix should be stripped before parsing the string as JSON.
I was wondering if you could extend the service with an update for the above and release it.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We are using a prefix before sending back the JSON responses in our API like in the example below:
)]}',
{"data": "wow"}
note that the above prefix is in fact ")]}',\n" but sometimes the white spaces are stripped out and it's only ")]}',"
"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."
This prefix should be stripped before parsing the string as JSON.
I was wondering if you could extend the service with an update for the above and release it.
The text was updated successfully, but these errors were encountered: