Third-Party Content Detection in Web Applications
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Web applications face issues with third-party content that can become unavailable, change, or disrupt the host application, leading to frame breaking and other scripting problems, which the publisher has no control over and can cause unintended termination or redirection of the host application.
Innovation Solution
A method and media for detecting third-party content in web applications, analyzing its existence, availability, and potential disruption before rendering, allowing for modifications such as removal, substitution, or user notification, using software on both server and client-side computers to prevent issues before they affect the user.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If third-party content is embedded in web pages, then content diversity and functionality are improved, but reliability and stability deteriorate due to frame breaking and scripting disruptions
Solution Approach 1:
The system performs preliminary detection of third-party content before it is rendered in the web browser. The detection occurs during page generation or caching, identifying potentially disruptive content such as frame-breaking scripts before they can affect the host application. This advance detection allows the system to take preventive actions without compromising the embedded content functionality.
Solution Approach 2:
The patent introduces an intermediary detection layer between the third-party content source and the host web application. This intermediary system analyzes the third-party content for disruptive characteristics (such as frame-breaking scripts) and determines whether to allow, block, or modify the content before it reaches the user's browser. This mediator resolves the contradiction by filtering harmful content while preserving legitimate embedded content.
2Adaptability or versatility
If third-party content is allowed to change dynamically, then adaptability is improved, but reliability deteriorates due to inaccessible or unavailable content
Solution Approach 1:
The system implements feedback mechanisms that monitor the status of third-party content over time. When content becomes inaccessible, unavailable, or changes in ways that disrupt the host application, the detection system identifies these changes and triggers appropriate responses. The feedback loop allows the system to adapt to content changes while maintaining reliability through continuous monitoring and corrective actions.
Solution Approach 2:
The detection system performs preliminary checks on third-party content to establish baseline characteristics and expected behavior. When content changes occur, the system compares current content against the baseline to detect problematic changes before they affect user experience. This preliminary establishment of content norms enables the system to reliably identify and respond to adverse changes while allowing legitimate content updates.
3Reliability
If detection and analysis of third-party content is performed, then reliability is improved, but device complexity increases due to server and client-side software requirements
Solution Approach 1:
The detection system is segmented into distinct server-side and client-side components, each with specific detection functions. The server-side software performs initial detection and analysis during content generation or caching, while the client-side browser plugin performs final verification before rendering. This segmentation distributes the complexity across multiple components rather than concentrating it in a single system, making the overall solution more manageable and scalable.
Data Source
AI summary
A media and method for detecting third-party content in web pages is provided. Computer software operates on a server or a client-side computer to identify and analyze third-party links and contents in web pages to determine if a third-party content sill exists, is available, has changed, or disrupts a web browser. A third-party link or content can be removed, changed, or replaced. A user can be notified or given an option to handle changed third-party content. The server may remove the third-party link or content by changing an HTML file for the web page. The client-side computer may remove the third-party link or content by dynamically changing the rendered web page before it is displayed to the user.