How secure is cross-site scripting with Kaazing?
Before HTML 5, browsers enforced a “same-origin” access policy to avoid cross-site scripting attacks. By implementing cross-origin resource sharing, Web applications that use Kaazing Enterprise Gateway can now access content that could theoretically have a different domain, scheme, host, or port. Rest assured, however, Kaazing is as paranoid about security as you are. Kaazing Enterprise Gateway aggressively secures content. The server component is secured using a “white list,” which means that each gateway service is by default denied access to cross-origin content. In addition, Kaazing Enterprise Gateway’s cross-site JavaScript bridge component implements the new W3C Cross-Origin Resource Sharing specification.
