Client-Side Security Script Offloads Web Content Filtering
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Content filtering services implemented as proxy servers face processing power limitations, leading to potential denial of service (DoS) and exposure to unfiltered data for client terminals when traffic volume exceeds capacity, as they must analyze all HTTP requests, causing bottlenecks and increased complexity.
Innovation Solution
A content filtering service is provided through a security script distributed by a server for local execution on client terminals, using JavaScript or similar browser scripts to analyze and filter content based on predefined rules, eliminating the need for intermediate processing and reducing server load by allowing direct traffic forwarding.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If content filtering is implemented as a proxy server that analyzes all HTTP requests, then security filtering capability is improved, but server processing load increases and bandwidth efficiency deteriorates
Solution Approach 1:
The patent extracts the content filtering function from the proxy server and implements it as client-side JavaScript code. The security filtering logic is taken out from the server environment and executed locally in the user's browser, thereby reducing server processing load while maintaining filtering capability.
Solution Approach 2:
The client terminal performs content filtering autonomously using locally executed JavaScript code. Each user's browser independently filters content without requiring server-side analysis of every HTTP request, enabling self-service filtering that scales without increasing server load.
2Reliability
If a proxy server analyzes every new HTTP request and page, then content security is improved, but response time increases and productivity decreases
Solution Approach 1:
The filtering analysis function is extracted from the proxy server and executed client-side. This eliminates the additional network round-trip time to the proxy server for each request, as filtering now occurs locally in the browser without requiring server communication for every page or dynamic request.
3Ease of operation
If the proxy server terminates original TCP connections and forwards requests, then filtering control is improved, but device complexity and bandwidth efficiency worsen
Solution Approach 1:
The TCP connection termination and request forwarding functions are extracted from the proxy server. The client-side JavaScript directly establishes connections to target servers and performs filtering locally, eliminating the need for complex proxy infrastructure that terminates and re-establishes connections.
Solution Approach 2:
The patent introduces a lightweight intermediary mechanism where the client-side JavaScript acts as the mediator between the user and content sources. Instead of a heavy proxy server mediating all connections, the browser-based script provides intermediary filtering functionality with minimal infrastructure overhead.
4Productivity
If proxy servers handle high traffic volume, then service coverage is improved, but processing capacity is exceeded leading to denial of service
Solution Approach 1:
Each client terminal independently performs content filtering using locally executed JavaScript code. This distributes the processing capacity across numerous client devices rather than concentrating it in a single proxy server, enabling the system to handle high traffic volumes without overwhelming a centralized processing point.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A system of providing a content filtering service, comprising: a network interface adapted to receive from a client terminal via a network a request for retrieving network data from at least one network resource; a store code for storing a code to transmit to the client terminal a client side security script in response to the request; and a processor, connected to the network interface and the store code, and adapted to execute the code for transmitting the client side security script to the client terminal; wherein the client side security script is adapted to be interpreted at the client terminal for authenticating the rendering of at least part of the network data from the at least one network resource.