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
Wrapping content in callback( without quotes/escaping it works well for json content, however it does not work for e.g. html. When trying to pull html cross domain with jsonp (with this module) result is callback(<html...</html>) without any quotes and/or escaping.
We either need a flag of some kind or some other method (including content detection) to determine if the returned content is pure json or something else, and if something else, wrap it in quotes/escape contents.
The text was updated successfully, but these errors were encountered:
@bjovanovic Yes, we could add an nginx configuration directive to enable a mode that ngx_xss always quote the response as JSON strings. Will you contribute a patch for this?
@agentzh Not really super skilled in c/writing stuff in nginx plugins, so not sure I would know how to do this production quality.
Also, not sure that a simple flag would do.. For instance we do want to be able to GET both JSON and HTML files cross domain in our project - for different purposes.
Wrapping content in callback( without quotes/escaping it works well for json content, however it does not work for e.g. html. When trying to pull html cross domain with jsonp (with this module) result is callback(<html...</html>) without any quotes and/or escaping.
We either need a flag of some kind or some other method (including content detection) to determine if the returned content is pure json or something else, and if something else, wrap it in quotes/escape contents.
The text was updated successfully, but these errors were encountered: