Access Request Processing via Domain Name Multiplexing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current HTTP2 technologies face high costs for modifying source stations and slow access speeds for HTTP1 users due to multiple TCP connection establishments and SSL negotiations, especially when handling multiple domain names.
Innovation Solution
A server method that adjusts domain names of sub-resource requests to a preset protocol type supporting multiplexing, allowing multiple requests to share a single connection, thereby increasing access speed without modifying the source station.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If multiple domain names are adopted for sub-resources, then the loading speed of sub-resources can be increased through multiplexing, but the TCP connection establishment and SSL negotiation handshake have to be performed several times which consumes more time
Solution Approach 1:
The patent introduces a mediator component that intercepts sub-resource requests and redirects them to a unified domain name. This mediator translates multiple original domain names into a single unified domain name, allowing all sub-resources to share one TCP connection and SSL session, thereby eliminating repeated connection establishments and handshakes while maintaining the ability to load multiple sub-resources in parallel through HTTP2 multiplexing
Solution Approach 2:
The patent merges multiple domain names into a single unified domain name for handling sub-resource requests. By combining multiple separate connection channels into one unified channel that supports HTTP2 multiplexing, the system achieves both connection reuse (reducing TCP/SSL overhead) and parallel resource loading (maintaining speed), thus resolving the contradiction between connection establishment time and loading speed
2Speed
If source station is modified to implement HTTP2 multiplexing, then the access speed can be improved, but the cost for modifying the source station is high and HTTP1 users are affected
Solution Approach 1:
The patent segments the system into two parts: the source station that remains unchanged and continues serving HTTP1 users, and a separate intermediary component that handles HTTP2 protocol conversion and domain name translation. This segmentation allows HTTP2 multiplexing benefits to be achieved without modifying the source station, thus reducing modification costs and avoiding impact on HTTP1 users while still improving access speed for HTTP2 clients
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The present disclosure relates to a network technology, and discloses a method, a device and a server for processing an access request. The method for processing an access request comprises: obtaining a response content corresponding to the access request from a source station according to a URL of the access request, when receiving the access request sent by a client terminal (101); adjusting domain names of at least two sub-resource requests in the response content to be a same domain name of a preset protocol type, and returning the adjusted response content to the client terminal, wherein, the domain name of the preset protocol type is a domain name supporting multiplexing (102); restoring, when receiving a sub-resource request having the same domain name sent by the client terminal, the domain name of the sub-resource request to an original domain name of the sub-resource request (103); and obtaining a sub-resource content corresponding to the sub-resource request from the source station according to the original domain name of the sub-resource request, and returning the sub-resource content to the client terminal (104). In the present application, the access speed of the users may be increased without user's perception; and there is no necessity to modify the source station.