Subordinate Request Web Page Logging
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing logging systems face inefficiencies in handling a large number of subordinate HTTP requests, as they are difficult to attribute accurately to the correct base web page in real time, leading to noise and distraction in log entries.
Innovation Solution
The technology uses the HTTP referer header field to attribute subordinate HTTP URL requests to the correct base web page in real time, compactly logging these requests by accumulating statistics for groups of subordinate requests and persisting them with the base web page log entry.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If subordinate HTTP requests are logged individually, then complete request information is captured, but storage space is consumed and log noise increases
Solution Approach 1:
The patent merges multiple subordinate HTTP requests into a single aggregated log entry by grouping requests that share common characteristics (same base URL, same time window). This combining approach reduces the total number of log entries while preserving essential information about request patterns, thereby reducing storage consumption without complete loss of request information.
Solution Approach 2:
Instead of logging each subordinate request individually and then filtering, the patent inverts the approach by first aggregating requests into groups and then logging only the aggregated results. This inversion fundamentally changes the logging strategy from detailed individual tracking to pattern-based summary logging, reducing storage requirements while maintaining analytical value.
2Measurement precision
If subordinate HTTP requests are logged in real time, then accurate attribution to base web pages is achieved, but computational resources are consumed
Solution Approach 1:
The patent applies preliminary action by pre-establishing grouping criteria and aggregation rules before logging occurs. By defining in advance how requests should be grouped (by base URL, time window, other characteristics), the system avoids complex real-time analysis while maintaining accurate attribution. The grouping logic is prepared beforehand, reducing computational burden during actual logging operations.
Solution Approach 2:
The patent uses copying by creating simplified representations of request groups rather than processing complete detailed information for each request. Each aggregated log entry contains essential attribution information (base URL, request count, time window) as a compact copy of the group's characteristics, reducing computational resources needed while maintaining attribution accuracy.
3Loss of information
If all subordinate requests are tracked individually, then detailed analytics are available, but log noise and distraction increase
Solution Approach 1:
The patent applies segmentation by dividing the log output into two distinct layers: aggregated summary views that reduce noise for general analysis, and detailed individual request data that can be accessed on-demand for specific investigations. This segmentation allows the system to present clean aggregated statistics while preserving detailed information when needed, reducing log noise without losing analytics capability.
Solution Approach 2:
The patent implements partial action by logging aggregated information for routine monitoring while maintaining the capability to retrieve detailed individual request data when specifically needed. This partial logging approach reduces everyday log noise while preserving detailed analytics capability on-demand, avoiding the need to log all individual requests continuously.
Data Source
AI summary
The technology disclosed works in real time, as base and subordinate HTTP and HTTPS URL requests are received, to attribute subordinate requests to base web pages. The main case uses the “referer” or “referrer” HTTP header field for attribution, directly and through a referrer hierarchy to the base web page. A second case, which minimizes false generation of base web page log entries, involves small files, such as cascading style sheets (CSS) files, that often have a blank or no referrer field.