Shared Error Searching for HTTP Requests

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Unauthorized access to web resources occurs when HTTP requests contain malicious elements, such as null bytes, which are interpreted differently by high-level web application codes, leading to unpredictable behavior and exposure of protected data.

Innovation Solution

A shared error searching system that combines error detection efforts by tracking progress and results for HTTP request components, allowing for a single pass search across multiple error types, thereby preventing re-checking of already evaluated portions of requests and enhancing security by denying or logging improper requests.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple separate error detection operations are performed on different request string components, then each error type can be detected thoroughly, but the number of search operations increases and processing time is extended

Engineering Contradiction:
Improveerror detection completenessVSAvoidrequest processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent combines multiple separate error detection operations into a single unified search operation. The system performs one search across the entire request string that simultaneously detects multiple error types (null bytes, improper formatting, etc.) in multiple string components (address, query string, post body), replacing what would otherwise be multiple separate search operations.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The error detection system is designed with multi-functionality to handle various error types and request components through a single operational framework. The unified search mechanism serves multiple purposes: detecting null bytes, identifying improper formatting, validating different string components, and preventing unauthorized access, all within one search operation.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Reliability

If multiple separate error detection operations are performed on HTTP request components, then comprehensive error coverage is achieved, but the complexity of the detection system increases

Engineering Contradiction:
Improveerror detection coverageVSAvoiddetection system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges multiple error detection functionalities into a single unified search operation. Instead of implementing separate detection mechanisms for null bytes, formatting errors, and other malformations in different request components, the system uses one integrated search that handles all error types across all string components simultaneously, reducing system complexity.

Inventive Principle:
Principle #5Merging (Combining)

3Productivity

If a single pass search is performed across multiple error types, then the number of search operations is reduced, but the ability to detect all error types may be compromised

Engineering Contradiction:
Improvesearch operation efficiencyVSAvoiderror detection accuracy
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The unified search operation is designed with multi-functionality to maintain comprehensive error detection capability. The search mechanism simultaneously identifies multiple error types (null bytes, improper formatting, invalid characters) across multiple request string components within a single pass, ensuring both efficiency and thorough detection without compromising accuracy.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS8516313B2Shared error searching
Publication Date: 2013.08.20 ORACLE INT CORP
  • US8516313B2 patent drawing
  • US8516313B2 patent drawing
  • US8516313B2 patent drawing

AI summary

Systems, methods, and other embodiments associated with shared error searching for web resource requests are described. A web resource request that includes one or more request strings is received and a error detection directive that identifies a first type of error to be located in a specified request string component is accessed. At least a portion of a first request string that corresponds to the specified request string component is searched, in a single pass, for the first type of error and other types of errors. Results with respect to the first error type are returned while occurrences of the first and other types of errors for are recorded for responding to subsequent error detection directives. Thus, a subsequent error detection directive for the other types of errors in the first request string component may be processed without re-searching the portion of the first request string already searched with respect to the first error detection directive.