CN111147583A - HTTP redirection rewriting method and device - Google Patents

HTTP redirection rewriting method and device Download PDF

Info

Publication number
CN111147583A
CN111147583A CN201911377017.8A CN201911377017A CN111147583A CN 111147583 A CN111147583 A CN 111147583A CN 201911377017 A CN201911377017 A CN 201911377017A CN 111147583 A CN111147583 A CN 111147583A
Authority
CN
China
Prior art keywords
address
redirection
load balancing
http
server
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN201911377017.8A
Other languages
Chinese (zh)
Inventor
李亮
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hangzhou DPTech Technologies Co Ltd
Original Assignee
Hangzhou DPTech Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hangzhou DPTech Technologies Co Ltd filed Critical Hangzhou DPTech Technologies Co Ltd
Priority to CN201911377017.8A priority Critical patent/CN111147583A/en
Publication of CN111147583A publication Critical patent/CN111147583A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/02Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1001Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004Server selection for load balancing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/56Provisioning of proxy services
    • H04L67/563Data redirection of data network streams

Abstract

The present specification provides a method and an apparatus for HTTP redirection rewriting, wherein the method includes: receiving an HTTP request sent by a client, and recording a load balancing equipment address in the HTTP request; forwarding the HTTP request to a server, and receiving an HTTP response returned by the server; the HTTP response contains redirection information; and if the redirection address in the redirection information is inconsistent with the load balancing equipment address, replacing the redirection address with the load balancing equipment address. To automatically overwrite and thereby avoid manually overwriting large amounts of redirection information.

Description

HTTP redirection rewriting method and device
Technical Field
The present disclosure relates to the field of internet technologies, and in particular, to a method and an apparatus for HTTP redirection.
Background
In a network using a load balancing technique, a client establishes a connection with a server through load balancing equipment. After the client sends an HTTP (Hyper Text Transfer Protocol) request to the server, the server needs to redirect to another path of the server if the server cannot provide corresponding service data. At this time, the server may include redirection information in the HTTP response, so that the client can acquire the required service data according to the redirection information. The redirection information contains the IP address of the server, and the client can only establish connection with the IP address of the corresponding service in load balancing and cannot establish connection with the IP address of the server directly. Therefore, the redirection information needs to be rewritten and modified into an address that the client can access in a connected manner, so that the client can acquire the required data through the load balancing device.
In the related HTTP redirection rewriting technology, the related address field of the redirection information in the HTTP response message is manually rewritten. The mode has high labor cost, low efficiency and easy error.
Disclosure of Invention
At least one embodiment of the present specification provides an HTTP redirection rewriting scheme to automatically rewrite redirection information that needs to be rewritten.
In a first aspect, a method for HTTP redirection rewriting is provided, where the method includes:
receiving an HTTP request sent by a client, and recording a load balancing equipment address in the HTTP request;
forwarding the HTTP request to a server, and receiving an HTTP response returned by the server; the HTTP response contains redirection information;
and if the redirection address in the redirection information is inconsistent with the load balancing equipment address, replacing the redirection address with the load balancing equipment address.
In a second aspect, an HTTP redirection rewriting apparatus is provided, the apparatus including:
the request processing module is used for receiving an HTTP request sent by a client and recording a load balancing equipment address in the HTTP request;
the response processing module is used for forwarding the HTTP request to a server and receiving an HTTP response returned by the server; the HTTP response contains redirection information;
and the rewriting module is used for replacing the redirection address with the load balancing equipment address under the condition that the redirection address in the redirection information is inconsistent with the load balancing equipment address.
In a third aspect, a computer device is provided, which includes a memory, a processor, and a computer program stored on the memory and executable on the processor, and when the processor executes the computer program, the processor implements the HTTP redirection rewriting method according to any embodiment of the present specification.
In a fourth aspect, a computer-readable storage medium is provided, on which a computer program is stored, which when executed by a processor, implements the steps of the HTTP redirection rewriting method according to any one of the embodiments of the present specification.
According to the technical scheme, in at least one embodiment of the specification, when the redirection address in the HTTP response is inconsistent with the load balancing device address, the redirection address is modified to the load balancing device address, so that the client can reconnect the load balancing device and obtain the required service data from the server again. The method can automatically rewrite the redirection information needing to be rewritten, thereby avoiding manually rewriting a large amount of redirection information, reducing the labor cost, improving the efficiency and being more accurate.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the specification.
Drawings
FIG. 1 is a flow diagram illustrating a method for HTTP redirect rewriting according to an exemplary embodiment;
FIG. 2 is a flow diagram illustrating another HTTP redirect rewrite method in accordance with an illustrative embodiment;
FIG. 3 is a schematic diagram illustrating an HTTP redirect rewriting apparatus in accordance with an illustrative embodiment;
fig. 4 is a schematic diagram illustrating a load balancing application scenario according to an example embodiment.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the specification, as detailed in the appended claims.
The terminology used in the description herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the description. As used in this specification and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, the first information may also be referred to as second information, and similarly, the second information may also be referred to as first information, without departing from the scope of the present specification. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
To facilitate understanding of the HTTP redirection rewrite method provided in this specification, the related terms will be first introduced.
Load balancing: load balancing is a set of servers (see fig. 4) composed of a plurality of servers, each server can independently provide the same service, an external request is distributed to one of the sets of servers through a certain load algorithm, the server provides service for a request device, highly reliable and highly stable service can be provided for the outside through balanced load, and the pressure of a single server is reduced.
HTTP (Hyper Text Transfer Protocol) Protocol: TCP/IP (Transmission Control Protocol/Internet Protocol) is a transport Protocol for transmitting hypertext from a web server to a local browser.
HTTP request: after the TCP three-way handshake is connected to the server, the client sends a request message, called an HTTP request, to the server.
HTTP response: after receiving the request of the client, the server returns a response message called HTTP response to the client.
URL (uniform resource locator ) redirection: also known as URL forwarding, is a technique to keep original links available when an actual resource, such as a single page, form, or entire application, is migrated under a new URL.
HTTP redirection: for URL redirection, the HTTP protocol provides a special form of response-HTTP redirection to perform such operations. This operation can be applied to a wide variety of targets: temporary jumps during website maintenance; permanent redirection to keep external links available after a website architecture change; a page indicating progress when uploading a file. In the HTTP protocol, the redirection operation is triggered by the server by sending a special response. The state code of the redirect response of the HTTP protocol is 3 xx. When the browser receives the redirection response, the browser adopts the new URL provided by the response and immediately loads the URL. In most cases, the redirection operation is not visible to the user, except for a small loss of performance.
The application scenario of the network using the load balancing technique is shown in fig. 4. In the network, the load balancing device provides uniform service to the outside and is a uniform IP address to the outside. The client can only establish connection with the load balancing device, but cannot directly establish connection with one server in the server cluster. For example, after the server 1 receives the access request forwarded by the load balancing device, if the returned response data includes redirection information, and the address of the redirection information points to the server 1. At this time, if the load balancing device directly forwards the response data to the client, the client may actively establish a connection with the server 1 when initiating the request again, which may result in a connection failure and a service interruption. Therefore, before forwarding the response data to the client, the address of the redirection information in the response data needs to be rewritten to the address of the load balancing device, so that the client is ensured to be connected with the load balancing device when revisiting, so as to obtain the required service data again according to the redirection information.
In the HTTP redirection rewriting method provided in this specification, when a redirection address included in an HTTP response returned by the server is inconsistent with an address of the load balancing device, the redirection address is automatically replaced with the address of the load balancing device, so that the client can request the required service data through the load balancing device again according to the redirection information. The method can automatically rewrite the redirection information needing to be rewritten, thereby avoiding manually rewriting a large amount of redirection information, reducing the labor cost, improving the efficiency and being more accurate.
The load balancing device in the embodiments of the present specification may be a physical device or a logical module; the server can be a physical or logical server, or two or more physical or logical servers sharing different responsibilities and cooperate with each other to realize various functions of the server in the embodiment of the application; the client can be a mobile phone, a tablet computer, a personal computer, a notebook computer and other devices. In this embodiment, specific implementation manners of the client, the load balancing device, and the server are not limited.
In order to make the HTTP redirection rewrite method provided in this specification clearer, a detailed description is given below of a scheme implementation procedure provided in this specification with reference to the accompanying drawings and specific embodiments.
Referring to fig. 1, fig. 1 is a flowchart illustrating an HTTP redirection rewriting method according to an embodiment provided in the present specification. The method is applied to the load balancing equipment.
As shown in fig. 1, the process includes:
step 101, receiving an HTTP request sent by a client, and recording a load balancing device address in the HTTP request.
And when the client needs to request service data, sending a corresponding HTTP request to the load balancing equipment. And after receiving the HTTP request, the load balancing equipment records the address of the load balancing equipment in the HTTP request. For example, the load balancing device records a host value in the HTTP request according to the quintuple information, and acquires the load balancing device address from the host value.
In one example, the load balancing device address comprises: the IP address of the load balancing device and the port of the load balancing device. The IP address of the load balancing equipment is the IP address used when the load balancing equipment establishes connection with the client; the port of the load balancing device is a port used when the load balancing device establishes connection with the client.
Step 102, forwarding the HTTP request to a server, and receiving an HTTP response returned by the server; the HTTP response includes redirection information.
The load balancing device forwards the HTTP request to a server in the server cluster through a certain algorithm. After receiving the HTTP request, the server returns a corresponding HTTP response to inform the client: the service data needed by the client needs to be acquired in other paths of the server again. That is, the HTTP response includes redirection information for informing the client of where to acquire the required service data.
Step 103, if the redirection address in the redirection information is inconsistent with the load balancing device address, replacing the redirection address with the load balancing device address.
The redirection information returned by the server includes the address of the request sent by the client during redirection, which may be a domain name, an IP address or port information. For example, the load balancing device may obtain redirection information from a location field in the HTTP response according to the quintuple information: a redirect address and redirect path information. In this step, if the address in the redirection information is not consistent with the address of the load balancing device, that is, the address in the redirection information points to the server. At this time, the load balancing device will replace the redirection address as the address of the load balancing device, i.e., make the redirection address point to the load balancing device. Therefore, when the client re-initiates the access request according to the redirection information, the client can actively access the load balancing equipment, and further can obtain the required service data through the load balancing equipment.
In one example, after replacing the redirection address with the load balancing device address, the method further includes: and forwarding the HTTP response to the client so that the client can retrieve the required data according to the redirection information contained in the HTTP response.
In the above example, after replacing the redirection address included in the HTTP response with the address of the load balancing device, the load balancing device forwards the modified HTTP response to the client. After receiving the HTTP response, the client may analyze an address (in this case, an address of the load balancing device) and redirection path information required for the access. The redirection path information is carried in the redirection information when the server returns the HTTP response, and is used for relocating the position of the service data required by the client. For example, after the client sends the access request to the load balancing device again by using the redirection information, the load balancing device forwards the access request to the server, and the server obtains the service data correspondingly needed by the client according to the redirection path carried in the redirection information.
Specific examples are such as: the redirection information returned by the server may be
"https:// mp. weixin. qq. com/s/Svs0Azgecfr4vgSEY0L1 QQ", wherein,
the part 'mp.weixin.qq.com' is a redirection address, and if the redirection address points to a load balancing device, the redirection address is replaced by the load balancing device; the "s/Svs 0Azgecfr4vgSEY0L1 QQ" part is redirection path information, which is not modified in any way in the HTTP redirection rewrite method provided in this specification. The server carries redirection path information in the return redirection information, so as to inform the client that the client should re-access the path of the server.
As another example, the redirection information returned by the server may be "http//: 192.168.1.1:80/1225/kjsb ", where the" 192.168.1.1:80 "portion is the redirect address and the" 1225/kjsb "portion is the redirect path information. If the destination IP address "192.168.1.1" and the destination port "80" in the redirect address point to the server, the destination IP address and the destination port are rewritten to the IP address and 443 port of the load balancing device (assuming that the HTTPS protocol is used between the load balancing device and the client, 443 port is used).
In the HTTP redirection rewriting method of this embodiment, when the redirection address in the redirection information returned by the server is different from the address of the load balancing device, the redirection address is automatically replaced with the address of the load balancing device. That is, when the redirection address points to the server, the redirection address is rewritten to an address pointing to the load balancing device, and when the client re-initiates the HTTP request according to the redirection information, the client re-acquires the required service data from the server through the load balancing device. According to the method, when the redirection address points to the server, the redirection address is automatically modified to the address pointing to the load balancing equipment, so that a large amount of redirection information is prevented from being manually rewritten, the labor cost is reduced, the efficiency is improved, and the method is more accurate.
In an example, in step 103, replacing the redirection address with the load balancing device address when the redirection address in the redirection information is inconsistent with the load balancing device address includes: if the destination port in the redirection address is consistent with the port of the server, replacing the destination port with the port of the load balancing equipment; and/or replacing the destination IP address with the IP address of the load balancing equipment if the destination IP address in the redirection address is consistent with the IP address of the server.
In the above example, if the destination port in the redirection address returned by the server is the port of the server, that is, the redirection address directly points to the server, the destination port in the redirection address is replaced with the port of the load balancing device, that is, the redirection address is made to point to the load balancing device. And if the destination IP address in the redirection address returned by the server is the IP address of the server, namely, the redirection address points to the server, replacing the redirection address with the IP address of the load balancing equipment, namely, pointing the redirection address to the load balancing equipment. If the destination port and the destination IP address in the redirection address both point to the server, replacing the destination port in the redirection address with the port of the load balancing equipment; and replacing the destination IP address with the IP address of the load balancing equipment so that the redirection address points to the load balancing equipment.
For example, the redirection address returned by the server includes domain name a and port B, where domain name a is the same as the domain name in the HTTP request, and port B is the port of the server, that is: and if the domain name A points to the load balancing equipment and the port B points to the server, replacing the port B with the port of the load balancing equipment.
For example, the redirection addresses returned by the server are domain name a and 80 ports, and if an HTTPS protocol is used between the client and the load balancing device, 443 port is used; the load balancing device and the server adopt HTTP protocol, and 80 ports are used. At this time, the 80 port is replaced by 443 port to satisfy the access of the HTTPS protocol normal connection between the client and the load balancing device.
For another example, the redirection addresses returned by the server are IP1 and port B, where IP1 and port B are the same as the IP and port of the server, i.e.: the redirection address points to the load balancing equipment; the redirect address is modified to the IP address and port of the load balancing device.
There is also a case where the redirect addresses returned by the server are IP1 and 80 ports, where IP1 is the IP address of the server and 80 ports are the ports used by the HTTP protocol between the load balancing device and the server, for example. Assuming that HTTPS protocol (using 443 port) is used between the client and the load balancing device, the redirect address is rewritten to the IP address and 443 port of the load balancing device.
In the HTTP redirection rewriting method of this embodiment, when a destination port in a redirection address returned by a server points to the server, the destination port is automatically rewritten to a port of a load balancing device; when the destination IP address in the redirection address points to the server, the destination IP address is automatically rewritten to the IP address of the load balancing equipment, so that the redirection address points to the load balancing equipment.
Referring to fig. 2, fig. 2 is a flowchart of another HTTP redirection rewriting method provided in this specification. As shown in fig. 2, the process may include:
step 101, receiving an HTTP request sent by a client, and recording a load balancing device address in the HTTP request.
Step 201, forwarding the HTTP request to a server, and receiving an HTTP response returned by the server.
The above steps are similar to the description of the related steps in fig. 1, and are not described again here.
In one example, after receiving the HTTP response returned by the server, the method further includes: determining that the HTTP response does not contain the redirection information according to a status code in the HTTP response; forwarding the HTTP response to the client.
In the above example, after receiving the HTTP response returned by the server, the load balancing device parses the status code, and determines whether the HTTP response includes redirection information according to the status code, and if not, directly forwards the response to the client, so that the client receives the required service response data.
Specific status code judgment, for example, if the status code in the HTTP response is 3XX, it is determined that the response contains redirection information; if the state code in the HTTP response is not 3XX, the response is determined not to contain redirection information, and the response is forwarded to the client.
Step 202, according to the status code in the HTTP response, determining that the HTTP response contains the redirection information.
And the load balancing equipment analyzes the received HTTP response, and if the status code is 3XX, the response is determined to contain the redirection information.
Step 203, if the redirection address in the redirection information is consistent with the load balancing device address, forwarding the HTTP response to the client.
If the redirection address is consistent with the load balancing device address, that is, the redirection address points to the load balancing device. At this time, the redirection address does not need to be modified, the client can directly access the load balancing device according to the redirection address, and the required service data is obtained from the server through the load balancing device.
In the HTTP redirection rewriting method of this embodiment, whether the response includes redirection information is determined by a status code in the HTTP response, and when the response includes the redirection information and the redirection address points to the load balancing device, the redirection address is not modified, and the response is directly forwarded to the client.
Fig. 3 illustrates an HTTP redirection rewriting apparatus provided in this specification, which may perform the HTTP redirection rewriting method according to any embodiment of the specification. The apparatus may include a request processing module 301, a response processing module 302, and a rewrite module 303. Wherein:
the request processing module 301 is configured to receive an HTTP request sent by a client, and record a load balancing device address in the HTTP request;
a response processing module 302, configured to forward the HTTP request to a server, and receive an HTTP response returned by the server; the HTTP response contains redirection information;
a rewriting module 303, configured to replace the redirection address with the load balancing device address when the redirection address in the redirection information is inconsistent with the load balancing device address.
The implementation process of the functions and actions of each module in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of at least one embodiment of the present specification. One of ordinary skill in the art can understand and implement it without inventive effort.
The present specification also provides a computer device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor is capable of implementing the HTTP redirection rewriting method of any embodiment of the present specification when executing the program.
The present specification also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, is capable of implementing the HTTP redirection rewrite method of any of the embodiments of the present specification.
The non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc., which is not limited in this application.
Other embodiments of the present description will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This specification is intended to cover any variations, uses, or adaptations of the specification following, in general, the principles of the specification and including such departures from the present disclosure as come within known or customary practice within the art to which the specification pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the specification being indicated by the following claims.
It will be understood that the present description is not limited to the precise arrangements described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present description is limited only by the appended claims.
The above description is only a preferred embodiment of the present disclosure, and should not be taken as limiting the present disclosure, and any modifications, equivalents, improvements, etc. made within the spirit and principle of the present disclosure should be included in the scope of the present disclosure.

Claims (9)

1. A hypertext transfer protocol (HTTP) redirection rewriting method, the method comprising:
receiving an HTTP request sent by a client, and recording a load balancing equipment address in the HTTP request;
forwarding the HTTP request to a server, and receiving an HTTP response returned by the server; the HTTP response contains redirection information;
and if the redirection address in the redirection information is inconsistent with the load balancing equipment address, replacing the redirection address with the load balancing equipment address.
2. The method of claim 1, wherein after replacing the redirection address with the load balancing device address, further comprising:
and forwarding the HTTP response to the client so that the client can retrieve the required data according to the redirection information contained in the HTTP response.
3. The method of claim 1, wherein the load balancing device address comprises: the IP address of the load balancing device and the port of the load balancing device.
4. The method of claim 1, wherein the step of replacing the redirection address with the load balancing device address when the redirection address in the redirection information is inconsistent with the load balancing device address comprises:
if the destination port in the redirection address is consistent with the port of the server, replacing the destination port with the port of the load balancing equipment;
and/or replacing the destination IP address with the IP address of the load balancing equipment if the destination IP address in the redirection address is consistent with the IP address of the server.
5. The method according to claim 1, wherein after receiving the HTTP response returned by the server, further comprising:
determining that the HTTP response does not contain the redirection information according to a status code in the HTTP response;
forwarding the HTTP response to the client.
6. The method according to claim 1, wherein after receiving the HTTP response returned by the server, further comprising:
determining that the HTTP response contains the redirection information according to a status code in the HTTP response;
and if the redirection address in the redirection information is consistent with the load balancing equipment address, forwarding the HTTP response to the client.
7. An HTTP redirect rewrite apparatus, the apparatus comprising:
the request processing module is used for receiving an HTTP request sent by a client and recording a load balancing equipment address in the HTTP request;
the response processing module is used for forwarding the HTTP request to a server and receiving an HTTP response returned by the server; the HTTP response contains redirection information;
and the rewriting module is used for replacing the redirection address with the load balancing equipment address under the condition that the redirection address in the redirection information is inconsistent with the load balancing equipment address.
8. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method of any of claims 1-6 when executing the program.
9. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 6.
CN201911377017.8A 2019-12-27 2019-12-27 HTTP redirection rewriting method and device Pending CN111147583A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911377017.8A CN111147583A (en) 2019-12-27 2019-12-27 HTTP redirection rewriting method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911377017.8A CN111147583A (en) 2019-12-27 2019-12-27 HTTP redirection rewriting method and device

Publications (1)

Publication Number Publication Date
CN111147583A true CN111147583A (en) 2020-05-12

Family

ID=70520955

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911377017.8A Pending CN111147583A (en) 2019-12-27 2019-12-27 HTTP redirection rewriting method and device

Country Status (1)

Country Link
CN (1) CN111147583A (en)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111988405A (en) * 2020-08-20 2020-11-24 杭州迪普科技股份有限公司 Message rewriting method of load balancing device and load balancing device
CN112492055A (en) * 2020-11-11 2021-03-12 浪潮商用机器有限公司 Method, device and equipment for redirecting transmission protocol and readable storage medium
CN113067824A (en) * 2021-03-22 2021-07-02 平安科技(深圳)有限公司 Data scheduling method, system, virtual host and computer readable storage medium
CN113805880A (en) * 2021-09-06 2021-12-17 南京联创信息科技有限公司 Method for solving request failure of https protocol under shiro framework

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140207968A1 (en) * 2013-01-23 2014-07-24 Cisco Technology, Inc. Server Load Balancer Traffic Steering
CN105939313A (en) * 2015-09-01 2016-09-14 杭州迪普科技有限公司 State code redirecting method and device
CN106878434A (en) * 2017-02-28 2017-06-20 杭州迪普科技股份有限公司 A kind of method and device of redirection
CN107070983A (en) * 2017-01-23 2017-08-18 天地融科技股份有限公司 A kind of load-balancing method, equipment and system forwarded based on address

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140207968A1 (en) * 2013-01-23 2014-07-24 Cisco Technology, Inc. Server Load Balancer Traffic Steering
CN105939313A (en) * 2015-09-01 2016-09-14 杭州迪普科技有限公司 State code redirecting method and device
CN107070983A (en) * 2017-01-23 2017-08-18 天地融科技股份有限公司 A kind of load-balancing method, equipment and system forwarded based on address
CN106878434A (en) * 2017-02-28 2017-06-20 杭州迪普科技股份有限公司 A kind of method and device of redirection

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111988405A (en) * 2020-08-20 2020-11-24 杭州迪普科技股份有限公司 Message rewriting method of load balancing device and load balancing device
CN111988405B (en) * 2020-08-20 2023-09-26 杭州迪普科技股份有限公司 Message rewriting method of load balancing device and load balancing device
CN112492055A (en) * 2020-11-11 2021-03-12 浪潮商用机器有限公司 Method, device and equipment for redirecting transmission protocol and readable storage medium
CN113067824A (en) * 2021-03-22 2021-07-02 平安科技(深圳)有限公司 Data scheduling method, system, virtual host and computer readable storage medium
CN113067824B (en) * 2021-03-22 2023-04-07 平安科技(深圳)有限公司 Data scheduling method, system, virtual host and computer readable storage medium
CN113805880A (en) * 2021-09-06 2021-12-17 南京联创信息科技有限公司 Method for solving request failure of https protocol under shiro framework

Similar Documents

Publication Publication Date Title
CN111147583A (en) HTTP redirection rewriting method and device
US10630771B1 (en) Content delivery network with network storage and support for on-demand content upload
US9871850B1 (en) Enhanced browsing using CDN routing capabilities
US8713365B2 (en) Re-establishing push notification channels via user identifiers
US9325785B2 (en) Device, system, and method for client-governed session persistency between one or more clients and servers of a data center
US10182126B2 (en) Multilevel redirection in a virtual desktop infrastructure environment
CN108881066B (en) Routing request method, access server and storage device
JP2018506936A (en) Method and system for an end-to-end solution for distributing content in a network
CN106657180B (en) Information transmission method and device for cloud service, terminal equipment and system
US8341285B2 (en) Method and system for transferring files
US9390156B2 (en) Distributed directory environment using clustered LDAP servers
CA2640696C (en) Storing and retrieving user context data
CN106911735B (en) Data acquisition method and device
US10645183B2 (en) Redirection of client requests to multiple endpoints
US20200344321A1 (en) Multiple Geography Service Routing
EP3313022B1 (en) Resending method and device for hypertext transfer request, and client
US11743236B2 (en) Generating an application-based proxy auto configuration
US20170054590A1 (en) Multi-Tenant Persistent Job History Service for Data Processing Centers
EP3298736B1 (en) Forwarding current request based on, at least in part, previous request(s)
CN111818179A (en) User request processing method and device, computing equipment and medium
EP2814220B1 (en) Apparatus and method for transmitting/receiving data in a mobile content network
CN111107039A (en) Communication method, device and system based on TCP connection
CN106911733B (en) Cloud proxy website access method and device
US11546405B2 (en) Methods for exposing mainframe data as a web service and devices thereof
JP2023522785A (en) Harmony Comprehensive Proxy Service

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
RJ01 Rejection of invention patent application after publication
RJ01 Rejection of invention patent application after publication

Application publication date: 20200512