HTTPS 302 Jumping via IP-to-Domain Hashing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The HTTPS protocol does not inherently support 302 jumping methods that use IP as a destination, leading to certificate verification failures and poor scalability in CDN systems when servers change, as existing methods require timely DNS updates.
Innovation Solution
A method and system that generate a jumping URL by converting an IP address of a content server to a prefix of a jumping domain name using predetermined rules, such as the Base32 algorithm, and combining it with a pre-registered domain name to form a jumping URL, which is then resolved by a DNS server to obtain the IP address, allowing seamless HTTPS support and improved scalability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If HTTPS protocol is used with 302 jumping method using IP as destination, then secure connection is established, but certificate verification fails because client uses IP as domain name for verification
Solution Approach 1:
The patent introduces a domain name as an intermediary between the IP address and the SSL certificate verification process. Instead of directly using the IP address in the 302 redirect, the system generates a domain name that maps to the IP address, allowing the SSL certificate to be verified against this domain name rather than the IP, thus resolving the certificate verification failure while maintaining HTTPS security
Solution Approach 2:
The patent segments the original 302 redirect process into two parts: first, generating a domain name from the IP address using a hashing algorithm; second, using this domain name in the SSL handshake and 302 redirect. This segmentation allows the SSL certificate verification to work with the domain name while the backend still uses the original IP address for content delivery
2Productivity
If existing 302 jumping method with IP destination is used in CDN systems, then direct server redirection is achieved, but scalability deteriorates when servers change requiring timely DNS updates
Solution Approach 1:
The patent performs preliminary action by pre-generating domain names from IP addresses using a hashing algorithm before any server changes occur. This pre-generated domain name structure allows for automatic resolution and redirection without requiring manual DNS updates when servers change, thus maintaining high productivity while improving scalability
Solution Approach 2:
The patent changes the parameter representation from direct IP addresses to hashed domain names. This parameter transformation allows the system to maintain efficient redirection (since the domain name directly maps to the IP through deterministic hashing) while improving scalability (since the hashed domain names can be generated on-demand without manual DNS configuration)
3Reliability
If domain name is added to include server ID for HTTPS jumping, then certificate verification can proceed, but system complexity increases and expansion becomes difficult
Solution Approach 1:
The patent implements self-service by using a deterministic hashing algorithm that automatically generates domain names from IP addresses. This eliminates the need for manual DNS configuration and management, as the domain names are generated on-demand based on the server's IP address, reducing system complexity while maintaining certificate verification capability
Solution Approach 2:
The patent creates a universal domain name generation mechanism that works across all servers in the CDN system. The same hashing algorithm can generate domain names for any IP address, making the system easily expandable to new servers without requiring separate DNS configuration for each server, thus reducing complexity while improving versatility
Data Source
AI summary
The present disclosure provides a jumping URL generating method, a jumping URL system, and a jumping server; a resolving method and a system for resolving a domain-name resolution request, and a DNS server; and a 302 jumping method and a network system that support HTTPS. A client terminal sends a first HTTP request. The jumping server specifies a content server, convert an IP address of the content server to a prefix of a jumping domain name, uses a service domain name as a suffix of the jumping domain name, combines the jumping domain name and a URL in the first HTTP to form the jumping URL, and sends the jumping URL to the client terminal. The client terminal requests for resolving of the jumping domain name. The DNS server recognizes a domain name in the domain-name resolution request and performs an inverse converting on the prefix of the jumping domain name to obtain an IP address of the content server and sends the IP address of the content server to the client terminal. The client terminal sends a second HTTP request containing the jumping URL to the content server; and sends an IP generated by resolving and in correspondence of the first HTTP request to the client terminal.