{'fraction_non_alphanumeric': 0.020855057351407715, 'fraction_numerical': 0.0, 'mean_word_length': 5.114649681528663, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Building Secure Web Mashups

Web applications that integrate content from multiple web sites within the user’s browser are becoming increasingly common. Although the socalled “same-origin policy” was designed to prevent such interactions from occurring, these applications, known as web mashups, use a variety of means to circumvent this policy. While mashups are quite popular among web users, they expose users to a variety of security risks. There have been several recent proposals for increasing the security of mashups. One approach involves the use of a new version of JavaScript with better security properties. Anther approach proposes that HTML be extended with security-oriented tags. Two more proposals offer methods of performing secure browser-side message-passing in unmodified browsers. Each of these proposals has some ideas that could be useful in a long-term solution to mashup security, but a convincing and complete solution has yet to be