In-Server HTTP Redirection for Bandwidth Optimization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing HTTP redirect technologies require clients to re-submit URL requests after receiving redirection commands, leading to increased network bandwidth usage, higher communication costs, and reduced response rates, especially in mobile networks, due to the need for multiple requests and lack of internal redirection capabilities within the server.

Innovation Solution

A method and system where the HTTP server internally identifies and processes redirections, sending the true URL content to the client without requiring the client to support redirection commands, by analyzing the HTTP response and submitting requests to either the target or redirected URLs as necessary.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If standardized HTTP redirect function is used, then clients can be redirected to relevant webpages, but network bandwidth is wasted and communication costs increase due to multiple requests

Engineering Contradiction:
Improveredirect capabilityVSAvoidnetwork bandwidth
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The server performs the redirect action in advance by including the final URL directly in the initial HTTP response body, eliminating the need for clients to issue subsequent requests to resolve redirects. This preliminary provision of the final destination resolves the contradiction by maintaining redirect adaptability while preventing the bandwidth waste that would result from multiple request-response cycles.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If standardized HTTP redirect function is used, then URL redirection can be achieved, but response rate is reduced due to client needing to re-submit requests

Engineering Contradiction:
Improveredirect functionVSAvoidresponse rate
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The server provides the final URL in the initial response, performing the redirect resolution before the client needs to act. This eliminates the sequential delay where the client must wait for the redirect response, then submit a new request, then wait for the final response. The redirect function is maintained while response rate is improved by removing the intermediate request-submission step.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If HTTP server returns redirection command, then clients can be directed to new URLs, but client-side redirection capability is required which complicates the client

Engineering Contradiction:
Improveredirect supportVSAvoidclient capability
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The redirect functionality is extracted from the client and moved to the server. Instead of the client receiving a redirect command and needing to process it independently, the server directly includes the final URL in the response body, making the redirect transparent to the client. This maintains the adaptability of URL redirection while eliminating the need for complex client-side redirect handling capabilities.

Inventive Principle:
Principle #2Taking out (Extraction)

4Measurement precision

If multiple requests are submitted for redirection, then accurate URL content can be obtained, but user experience deteriorates due to increased communication time

Engineering Contradiction:
ImproveURL content accuracyVSAvoidcommunication time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The server performs the redirect resolution in advance and includes the accurate final URL directly in the initial response. This eliminates the time loss associated with multiple request-response cycles while maintaining the accuracy of the URL content, as the server has already resolved the redirect chain before sending the response to the client.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9986056B2In-server redirection of HTTP requests
Publication Date: 2018.05.29 ALIBABA GROUP HOLDING LTD
  • US9986056B2 patent drawing
  • US9986056B2 patent drawing
  • US9986056B2 patent drawing

AI summary

A method and system for HTTP request service identify a true URL content regardless of whether the target URL is redirected, and send the true URL content to a client. The requesting and sending of the redirected URL content is done internally in the HTTP server system and do not require the client to have the ability to receive and execute a URL redirection command. The server system receives a URL request from the client and generates within the server a response to the URL request. If the response does not contain any redirection information, the true URL content includes the target URL content; and if the response contains redirection information indicating a redirected URL, the true URL content includes a redirected URL content associated with the redirected URL. The client receives the true URL content in either case by submitting a request for the target URL once.