302 Redirecting Method Using IP-to-Domain Conversion for HTTPS
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The HTTPS protocol does not inherently support 302 redirecting using an IP as a destination, leading to certificate verification failures and poor scalability in CDN systems that rely on HTTP 302 redirecting with IP destinations.
Innovation Solution
A method and system that generate a redirecting URL by converting an IP address of a content server to a prefix of a redirecting domain name using predetermined rules, such as the Base32 algorithm, and combining it with a pre-registered domain name to form a redirecting URL, which is then sent to a client terminal, allowing for domain-name resolution and HTTPS support.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If IP address is used as destination in 302 redirecting, then redirecting speed is improved, but certificate verification fails in HTTPS protocol
Solution Approach 1:
The patent introduces a domain name as an intermediary between the client terminal and the content server IP address. Instead of directly using IP address in HTTPS redirecting, the system converts IP address to a domain name format that includes the original domain name, allowing certificate verification to proceed successfully while maintaining redirecting functionality
Solution Approach 2:
The patent changes the parameter format from raw IP address to a constructed domain name format. By transforming the destination representation from numerical IP to textual domain name with specific structure, the system enables HTTPS protocol compatibility while preserving the ability to redirect to content servers
2Reliability
If server name is added to domain name for redirecting, then HTTPS compatibility is improved, but system scalability deteriorates
Solution Approach 1:
The patent creates a universal domain name construction rule that works across different scenarios. The constructed domain name format using original domain name as suffix can handle various content server changes without requiring system reconfiguration, making the solution universally applicable to different CDN scenarios
Solution Approach 2:
The patent performs preliminary domain name construction by incorporating the original domain name into the redirecting domain name structure. This preliminary action ensures that when content servers change, the system can handle updates through standard DNS mechanisms without requiring complex reconfiguration, thus improving scalability
3Reliability
If domain name is used instead of IP address, then certificate verification is improved, but redirecting accuracy deteriorates
Solution Approach 1:
The patent segments the domain name into distinct functional parts: the original domain name component and the constructed redirecting domain name component. This segmentation allows the system to maintain precise routing information while presenting a certificate-verified domain name to the client, thus preserving both accuracy and security
Data Source
AI summary
The present disclosure provides a generating method and a system for redirecting URL, a redirecting server, a resolving method and a system for resolving a domain-name resolution request, a DNS server, a 302 redirecting method that supports HTTPS, and a network system. A client terminal sends a first HTTP request. The redirecting server specifies a content server, convert an IP address of the content server to a prefix of a redirecting domain name, uses a service domain name as a suffix of the redirecting domain name, combines the redirecting domain name and a URL in the first HTTP to form the redirecting URL, and sends the redirecting URL to the client terminal. The client terminal requests for resolving of the redirecting 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 redirecting 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 redirecting URL to the content server; and sends an IP generated by resolving and in correspondence of the first HTTP request to the client terminal.