CN111666514A - Data processing method and device for realizing cross-domain request at webpage end and related equipment - Google Patents

Abstract

The invention discloses a data processing method, device, computer equipment and storage medium for realizing cross-domain request on a webpage, which are applied to the field of computer technology and are used for improving the scalability and security of realizing cross-domain request on the webpage. The method provided by the present invention includes: receiving a service request message initiated by a client through a web page through a pre-deployed proxy service, the proxy service is deployed on a server with the same domain name as the web page, and the proxy service on the server passes through The pre-created dedicated channel receives the service request message; parses the address variable carried in the header of the service request message; obtains the value of the address variable to obtain the target request address; forwards the service request message through the proxy service to the server of the domain name pointed to by the target request address; when receiving a response message returned by the server pointed to by the target request address, the proxy service sends the response message to the client using the dedicated channel.

Description

Data processing method, device and related equipment for realizing cross-domain request on web page

technical field

The present invention relates to the field of computer technology, and in particular, to a data processing method, device, computer equipment and storage medium for realizing cross-domain request on a web page.

Background technique

In the process of implementing network data requests, based on security considerations, browsers are set with a same-origin policy, that is, non-same-origin interface requests are not allowed. When the protocol, domain name, and port number used between the requester and the server are only If there is one difference, the requester and the server are considered to be non-same origin. For example, the front-end page whose URL is "http://www.baidu.com" requests a back-end interface provided by "http://weibo.com", for example: http://weibo.com/getUserInfo to query Weibo User information interface, this kind of cross-domain request is not allowed by the browser.

Cross-domain request is a real problem that almost every front-end developer faces, because in the project construction, it is necessary to access to other systems to some extent, which may be under the status quo that the front-end and back-end are separated, for example, the front-end project is deployed on the A server. , the domain name is http://a.com, and the back-end project is deployed on the B server, the domain name is http://b.com, the front-end page on the A server needs to call the interface on the B server, and it will not be accessed by the browser. Allowed, calling the browser directly will prompt an error.

In view of the limitation of non-same-origin cross-domain requests in browsers, the traditional cross-domain solutions are as follows:

(1) CORS (Cross-origin resource sharing), that is, setting on the B server to allow the A server to access, which belongs to the active setting of friendly access, but it is easy for hackers to forge the A server to access;

(2) Since in the browser, tags like img and script have no cross-domain restrictions, the back-end interface can be transformed into a script format that returns a script, the content is a function that returns a JS, and the real returned information As a function parameter, when the front-end page on the A server uses the script <script src="http://b.com.getUserInfo"></script>, when the script is loaded, the browser will automatically run its content, since its content is a function with actual parameters, it is equivalent to getting the real information returned by the backend. Although this method is feasible, it requires the backend to write more useless code;

(3) Build a server for forwarding page requests by means of "node" + "express". On the built server, cross-domain requests sent from pages with all domain names set with "*" are allowed to be forwarded, so that the web page can be forwarded to Server cross-domain access request. However, the communication channel between the page created in this way and the proxy server is public. On the one hand, the security of the requested data cannot be guaranteed. On the other hand, the proxy server can only be used for forwarding, which is not conducive to the function expansion of the project implementation.

SUMMARY OF THE INVENTION

Embodiments of the present invention provide a data processing method, device, computer equipment and storage medium for realizing cross-domain request on a web page, so as to solve the technical problem that the existing technology cannot realize cross-domain request under the premise of ensuring data security.

A data processing method for realizing a cross-domain request on a web page, the method comprising:

Receive a service request message initiated by a client through a web page through a pre-deployed proxy service, the proxy service is deployed on the server with the same domain name as the web page, and the proxy service on the server receives the service request message through a pre-created dedicated channel service request message;

Parse the address variable carried in the header of the service request message;

Get the value of the address variable to get the target request address;

Forward the service request message to the server of the domain name indicated by the target request address through the proxy service;

When receiving a response message returned by the server pointed to by the target request address, the proxy service sends the response message to the client using the dedicated channel.

A data processing device for realizing cross-domain request on a web page, the device comprising:

The receiving module is used to receive the service request message initiated by the client through the webpage through the pre-deployed proxy service, the proxy service is deployed on the server with the same domain name as the webpage, and the proxy service on the server is pre-created The dedicated channel to receive the service request message;

The parsing module is used to parse the address variable carried in the header of the service request message;

The address obtaining module is used to obtain the value of the address variable and obtain the target request address;

A forwarding module, used for forwarding the service request message to the server of the domain name indicated by the target request address through the proxy service;

The sending module is configured to send the response message to the client through the proxy service using the dedicated channel when receiving the response message returned by the server pointed to by the target request address.

A computer device, comprising a memory, a processor, and a computer program stored in the memory and running on the processor, when the processor executes the computer program, the above-mentioned web page implements data for cross-domain requests The steps of the processing method.

A computer-readable storage medium, the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, implements the steps of the above-mentioned data processing method for realizing a cross-domain request by a web page.

The data processing method, device, computer equipment and storage medium for realizing cross-domain requests on the webpage proposed in this application, receive service request messages from the client through the webpage through a pre-deployed proxy service, and the proxy service is deployed on the webpage. On the server with the same domain name, because the proxy service on the server receives the service request message through the pre-created dedicated channel, the transmitted data has higher security, and then parses the header of the service request message carrying the address variable, obtain the value of the address variable, obtain the target request address, and forward the service request message to the server of the domain name indicated by the target request address through the proxy service to realize cross-domain forwarding. When requesting a response message returned by the server pointed to by the address, the proxy service sends the response message to the client through the dedicated channel, so as to realize the communication interaction between the web client and the server of the domain name pointed to by the target request address. , high communication security.

Description of drawings

In order to illustrate the technical solutions of the embodiments of the present invention more clearly, the following briefly introduces the drawings that are used in the description of the embodiments of the present invention. Obviously, the drawings in the following description are only some embodiments of the present invention. , for those of ordinary skill in the art, other drawings can also be obtained from these drawings without creative labor.

1 is a schematic diagram of an application environment of a data processing method for implementing a cross-domain request on a web page according to an embodiment of the present invention;

2 is a flowchart of a data processing method for implementing a cross-domain request on a web page according to an embodiment of the present invention;

3 is a flowchart of a data processing method for implementing a cross-domain request on a web page in another embodiment of the present invention;

FIG. 4 is a flowchart of step 105 in the data processing method for realizing cross-domain request on the web page according to an embodiment of the present invention;

5 is a schematic structural diagram of a data processing apparatus for implementing a cross-domain request on a web page according to an embodiment of the present invention;

FIG. 6 is a schematic diagram of a computer device in an embodiment of the present invention.

Detailed ways

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, but not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

The data processing method for realizing cross-domain request on the webpage provided by the present application can be applied in the application environment as shown in FIG. 1 , wherein the server A communicates with the client device and the server B through the network. The client devices include but are not limited to various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices. Server A and Server B can be implemented as independent servers or server clusters composed of multiple servers.

In one embodiment, as shown in FIG. 2 , a data processing method for realizing cross-domain requests on a web page is provided, and the method is applied to the server A in FIG. 1 as an example to illustrate, including the following steps:

S101. Receive a service request message initiated by a client through a webpage through a pre-deployed proxy service, the proxy service is deployed on a server with the same domain name as the webpage, and the proxy service on the server passes through a pre-created dedicated channel Receive the service request message.

In one of the embodiments, the step of deploying the proxy service on the server includes:

Configure the name of the package management tool and the address of the middleware contained in the service request message. The package management tool is such as the npm management tool, and the middleware can be understood as a server for forwarding the service request message. The middleware play the role of intermediate forwarding;

The data part of the service request message is parsed by the package management tool corresponding to the name of the package management tool to obtain the address of the middleware and the target request address;

When the address of the middleware is the same as the address of the local end, the processing method after parsing the service request message is configured to forward the service request message to the server of the domain name indicated by the resolved target request address.

According to a usage scenario of this embodiment, for example: create a new app.js file, and then enter the programming code of the proxy service in the app.js file, which specifically includes introducing the package management tool express npm package, and introducing the message content parsing npm package, The server-side network requests the npm package, uses the URL in the message content to parse the middleware, and on the server, starts the proxy service through the nodeapp.js command. When monitoring the requests sent by all web clients whose domain name is A, obtain the message content of this request, obtain the actual target address of this request for request forwarding, then forward this request on the server, and return the forwarding success to the client or failed status.

In one of the embodiments, the step of deploying the proxy service on the server further includes:

Configure the port number for monitoring the service request message. For example, the port number for monitoring the service request message can be configured as "3000".

S102. Parse the address variable carried in the header of the service request message.

In one embodiment, the address variable included in the header of the service request message may be represented by destUrl.

S103: Obtain the value of the address variable to obtain the target request address.

In this embodiment, by encapsulating the target request address in the header of the service request message, rather than in the body part of the service request message, the request parameters submitted by the developer can be prevented from using the same parameter as the address variable, thereby avoiding The value of the request parameter submitted by the developer overrides the target request address included in the address variable. On the one hand, the response timeout caused by the server not being able to obtain the target request address actually included in the address variable can be avoided, and on the other hand, the processing capability of the server to realize cross-domain requests can be improved.

S104, forward the service request message to the server of the domain name indicated by the target request address through the proxy service.

The server of the domain name pointed to by the target request address is server B in FIG. 1 .

In one of the embodiments, the step of deploying the proxy service on the server further includes:

Configure the status code to be fed back to the client when forwarding the service request packet fails.

The configured status code is, for example, "500".

According to a usage scenario of this embodiment, for example, the front-end page of http://www.baidu.com from the client requests the interface http://weibo.com provided by http://weibo.com for querying microblog user information /getUserInfo, because the browser prohibits the client page from directly accessing the user information interface of Weibo based on the security consideration policy, to solve this problem, a proxy service can be pre-deployed on the same server as the domain name of the front-end page, that is, the Baidu server, and in the An exclusive channel is built between the proxy service and the client page, which is used to receive the service request message from the front-end page of the domain name to access the microblog server, parse the target request address from the header of the service request message, and The service request message is forwarded to the server of the microblog, so far, the forwarding processing of the cross-domain request message is realized.

S105. When receiving a response message returned by the server pointed to by the target request address, send the response message to the client through the proxy service using the dedicated channel.

In one embodiment, the data processing method for realizing cross-domain request by the webpage further includes:

When forwarding the service request message to the server of the domain name indicated by the target request address fails, the first status code fed back to the client, for example, "500";

When sending the response message to the client using the dedicated channel fails, a second status code, such as "600", is fed back to the server.

The data processing method for realizing a cross-domain request by a web page proposed in this embodiment receives a service request message initiated by a client through a web page through a pre-deployed proxy service. The proxy service is deployed on the server with the same domain name as the web page. The proxy service on the server receives the service request message through a pre-created dedicated channel, so that the transmitted data has higher security, and then parses the address variable carried in the header of the service request message to obtain the address variable value, get the target request address, and forward the service request message to the server of the domain name indicated by the target request address through the proxy service to realize cross-domain forwarding. When responding to a message, the proxy service sends the response message to the client using the dedicated channel, so as to realize the communication interaction between the web client and the server of the domain name indicated by the target request address, with high scalability and secure communication. Sex is high.

FIG. 3 is a flowchart of a data processing method for implementing a cross-domain request by a web page in another embodiment of the present invention. The following describes in detail a data processing method for implementing a cross-domain request by a web page in another embodiment of the present invention with reference to FIG. 3 , As shown in FIG. 3 , the data processing method for realizing cross-domain request on the webpage includes the above steps S101 to S104 , and the step S105 further includes the following steps S301 to S303 .

S301. When receiving the response message returned by the server pointed to by the target request address, parse the service data contained in the response message.

In one embodiment, the service data is generally stored in the body part of the response message, and the service data can be obtained by parsing the body part of the response message.

S302. Perform encryption processing on the parsed service data, and encapsulate the encrypted service data into the response message.

S303. Send the encrypted response message to the client through the proxy service using the dedicated channel.

In one of the embodiments, the communication allowed by the dedicated channel is identified by configuring the format of the request command at the request initiator, and parsing the request URL (Uniform Resource Locator, Uniform Resource Locator) contained in the request command at the request receiver. object, according to an implementation scenario of this embodiment, for example:

The request sent by the front-end page, its format is:

Request(http://a.com/proxy,header,data), where http://a.com/proxy is the request URL, and the communication objects allowed by the dedicated channel pointed to by this URL are fixed (unauthorized User modification), the header specifies the target address of this request, and its content is generally:

header:{

"destUrl": http://b.com/xxxx The destUrl field here cannot be changed

};

The data parameter is the message content required by the actual request address http://b.com/xxxx;

The request is divided into two, first to the http://a.com/proxy path, which is the route on the proxy server, the proxy server processes this request, and forwards the actual routing address by obtaining the destUrl field in the header and response.

The proxy service on the server provided in this embodiment exchanges data with the client through a pre-created dedicated channel, so that the user has greater data processing authority on the server, and can encrypt the business data in the response message, and can Avoid the theft of user business data and improve the security of data transmission.

FIG. 4 is a flowchart of step 105 in the data processing method for realizing cross-domain request on the webpage according to an embodiment of the present invention. As shown in FIG. 4 , the data processing method for realizing cross-domain request on the webpage includes the above steps S101 to S104 On the basis of , this step S105 further includes the following steps S401 to S403.

S401. Parse the request parameters contained in the response message.

In one of the embodiments, the request parameter may exist in the header of the response packet, or may exist in the body part of the response packet. Optionally, this step further includes parsing all the request parameters.

S402: Determine whether the request parameter includes a preset request parameter to be signed, and if so, perform a signing process on the corresponding request parameter.

In one embodiment, the preset request parameters to be signed can be preset by humans, and optionally, the data processing method for realizing cross-domain requests on the webpage further includes:

Receive the request parameters to be signed entered by the user;

The received request parameter is saved in the database list as the preset request parameter to be signed.

S403: Encapsulate the request parameter of the signature processing in the response message.

In the process of HTTP request interaction, request parameters are transmitted in the form of URL or request body. Due to the openness of HTTP requests, request parameters are easy to be intercepted and tampered with. The proxy service on the server provided in this embodiment uses a pre-created exclusive The channel exchanges data with the client, so that the user has greater data processing authority on the server, and signs the sensitive request parameters, and then requests the receiver to verify the request parameters to ensure that the two signatures are the same. Only after the signature verification is passed, business logic processing is allowed, which can prevent the request parameters from being intercepted and tampered with.

It should be understood that the size of the sequence numbers of the steps in the above embodiments does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.

In one embodiment, a data processing apparatus for implementing cross-domain requests on a webpage is provided, and the data processing apparatus for implementing cross-domain requests on the webpage corresponds to the data processing method for implementing cross-domain requests on the webpage in the above embodiment. As shown in FIG. 5 , the data processing apparatus 100 for realizing cross-domain request on the webpage includes a receiving module 11 , a parsing module 12 , an address obtaining module 13 , a forwarding module 14 and a sending module 15 . The detailed description of each functional module is as follows:

The receiving module 11 is configured to receive a service request message initiated by a client through a web page through a pre-deployed proxy service, the proxy service is deployed on the server with the same domain name as the web page, and the proxy service on the server is pre-configured. The created dedicated channel receives the service request message.

The parsing module 12 is configured to parse the address variable carried in the header of the service request message.

The address obtaining module 13 is configured to obtain the value of the address variable to obtain the target request address.

The forwarding module 14 is configured to forward the service request message to the server of the domain name indicated by the target request address through the proxy service.

The sending module 15 is configured to, when receiving a response message returned by the server pointed to by the target request address, send the response message to the client through the proxy service using the dedicated channel.

The data processing device for realizing cross-domain requests on the webpage side proposed in this embodiment receives the service request message initiated by the client through the webpage through the pre-deployed proxy service. The proxy service is deployed on the server with the same domain name as the webpage. The proxy service on the server receives the service request message through a pre-created dedicated channel, so that the transmitted data has higher security, and then parses the address variable carried in the header of the service request message to obtain the address variable value, get the target request address, and forward the service request message to the server of the domain name indicated by the target request address through the proxy service to realize cross-domain forwarding. When responding to the message, the proxy service sends the response message to the client using the dedicated channel, so as to realize the communication interaction between the web client and the server of the domain name indicated by the target request address, and the communication security is high.

In one embodiment, the data processing apparatus 100 for implementing cross-domain requests on the webpage further includes:

a first configuration module, configured to configure the name of the package management tool and the address of the middleware included in the service request message;

a parsing unit, configured to parse the data part of the service request message through the package management tool corresponding to the name of the package management tool, to obtain the address of the middleware;

The second configuration module is configured to, when the address of the middleware is the same as the address of the local end, configure the processing method after parsing the service request message to forward the service request to the server of the domain name indicated by the parsed target request address message.

In one of the embodiments, the data processing apparatus 100 for implementing cross-domain requests on the webpage further includes an encryption module;

The parsing module is also used to parse the business data contained in the response message;

The encryption module is used to encrypt the parsed service data, and encapsulate the encrypted service data into the response message;

The sending module 15 is specifically configured to send the encrypted response message to the client through the dedicated channel through the proxy service.

In this embodiment, the proxy service on the server interacts with the client through a pre-created dedicated channel, so that the user has greater data processing authority on the server, and the business data in the response message can be encrypted, which can prevent the user from The business data is stolen, which improves the security of data transmission.

In one embodiment, the data processing apparatus 100 for implementing cross-domain requests on the webpage further includes a judgment module and a signature module:

The parsing module is also used to parse the request parameters contained in the response message;

a judging module for judging whether the request parameter contains a preset request parameter to be signed, and if so, the corresponding request parameter is signed;

The signing module is used to encapsulate the request parameter of the signing processing in the response message.

In the process of HTTP request interaction, request parameters are transmitted in the form of URL or request body. Due to the openness of HTTP requests, request parameters are easy to be intercepted and tampered with. The proxy service on the server provided in this embodiment uses a pre-created exclusive The channel exchanges data with the client, so that the user has greater data processing authority on the server, and signs the sensitive request parameters, and then requests the receiver to verify the request parameters to ensure that the two signatures are the same. Only after the signature verification is passed, business logic processing is allowed, which can prevent the request parameters from being intercepted and tampered with.

Optionally, the data processing device for realizing cross-domain request on the webpage further includes:

The parameter receiving module is used to receive the request parameters to be signed entered by the user;

The parameter saving module is configured to save the received request parameter in the database list as the preset request parameter to be signed.

The meanings of "first" and "second" in the above modules/units are only to distinguish different modules/units, and are not used to define which module/unit has a higher priority or other limiting meanings. Furthermore, the terms "comprising" and "having", and any variations thereof, are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device comprising a series of steps or modules is not necessarily limited to those expressly listed Those steps or modules, but may include other steps or modules not explicitly listed or inherent to these processes, methods, products or devices, the division of modules appearing in this application is only a logical division , and there may be other division methods when implementing in practical applications.

For the specific limitation of the data processing apparatus for realizing the cross-domain request on the web page, please refer to the limitation on the data processing method for realizing the cross-domain request on the web page above, which will not be repeated here. Each module in the data processing apparatus for realizing cross-domain request on the web page can be implemented in whole or in part by software, hardware and combinations thereof. The above modules can be embedded in or independent of the processor in the computer device in the form of hardware, or stored in the memory in the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

In one embodiment, a computer device is provided, the computer device may be a server, and its internal structure diagram may be as shown in FIG. 6 . The computer device includes a processor, memory, a network interface, and a database connected by a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium, an internal memory. The nonvolatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the execution of the operating system and computer programs in the non-volatile storage medium. The database of the computer device is used to store the data involved in the data processing method for realizing the cross-domain request on the web page. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a data processing method for realizing a cross-domain request on a web page is realized.

In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and running on the processor. When the processor executes the computer program, the web page in the above embodiment realizes cross-domain implementation. Steps of the requested data processing method, such as steps 101 to 105 shown in FIG. 2 and other extensions of the method and extensions of related steps. Alternatively, when the processor executes the computer program, the functions of each module/unit of the data processing apparatus for realizing cross-domain requests on the webpage end in the above-mentioned embodiments, such as the functions of modules 11 to 16 shown in FIG. 5 , are implemented. In order to avoid repetition, details are not repeated here.

The processor may be a central processing unit (Central Processing Unit, CPU), other general-purpose processors, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf processor Programmable Gate Array (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The processor is the control center of the computer device, and uses various interfaces and lines to connect various parts of the entire computer device.

The memory can be used to store the computer program and/or module, and the processor implements the computer by running or executing the computer program and/or module stored in the memory and calling the data stored in the memory various functions of the device. The memory may mainly include a stored program area and a stored data area, wherein the stored program area may store an operating system, an application program required for at least one function (such as a sound playback function, an image playback function, etc.), etc.; the storage data area may store Data (such as audio data, video data, etc.) created according to the usage of the mobile phone, etc.

The memory may be integrated in the processor, or may be provided separately from the processor.

In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the data processing method for implementing a cross-domain request by a web page in the foregoing embodiment are implemented, for example, as shown in FIG. Steps 101 to 105 shown in 2 and other extensions of the method and extensions of related steps. Alternatively, when the computer program is executed by the processor, the functions of the modules/units of the data processing apparatus for realizing cross-domain requests on the webpage end in the above-mentioned embodiments, such as the functions of modules 11 to 15 shown in FIG. 5 , are implemented. To avoid repetition, details are not repeated here.

Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be implemented by instructing relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage In the medium, when the computer program is executed, it may include the processes of the above-mentioned method embodiments. Wherein, any reference to memory, storage, database or other medium used in the various embodiments provided in this application may include non-volatile and/or volatile memory. Nonvolatile memory may include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous chain Road (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

Those skilled in the art can clearly understand that, for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example. Module completion, that is, dividing the internal structure of the device into different functional units or modules to complete all or part of the functions described above.

The above-mentioned embodiments are only used to illustrate the technical solutions of the present invention, but not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: it is still possible to implement the foregoing implementations. The technical solutions described in the examples are modified, or some technical features thereof are equivalently replaced; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should be included in the within the protection scope of the present invention.

Claims (10)

1. A data processing method for realizing a cross-domain request on a web page, wherein the method comprises: Receive a service request message initiated by a client through a webpage through a pre-deployed proxy service, the proxy service is deployed on a server with the same domain name as the webpage, and the proxy service on the server passes through a pre-created proxy service. The dedicated channel receives the service request message; Parse the address variable carried in the header of the service request message; Obtain the value of the address variable to obtain the target request address; forwarding the service request message to the server of the domain name indicated by the target request address through the proxy service; When receiving a response message returned by the server pointed to by the target request address, the proxy service sends the response message to the client through the dedicated channel. 2. The data processing method for realizing a cross-domain request on a web page according to claim 1, wherein the step of deploying the proxy service on the server comprises: Configure the name of the package management tool and the address of the middleware contained in the service request message; The data part of the service request message is parsed by the package management tool corresponding to the name of the package management tool to obtain the address of the middleware; When the address of the middleware is the same as the address of the local end, the processing method after parsing the service request message is configured to forward the service request message to the server of the domain name indicated by the resolved target request address. 3. The data processing method for realizing a cross-domain request on a web page according to claim 1, wherein, when receiving the response message returned by the server pointed to by the target request address, the method further comprises: Parse the business data contained in the response message; The parsed service data is encrypted, and the encrypted service data is encapsulated into the response message. 4. The data processing method for realizing a cross-domain request on a web page according to claim 1, wherein, when receiving a response message returned by the server pointed to by the target request address, the method further comprises: Parse the request parameters contained in the response message; Determine whether the request parameters include preset request parameters to be signed, and if so, perform signing processing on the corresponding request parameters; The request parameter of the signature processing is encapsulated in the response message. 5. The data processing method for realizing a cross-domain request on a web page according to any one of claims 1 to 4, wherein the method further comprises: When forwarding the service request message to the server of the domain name indicated by the target request address fails to forward, the first status code fed back to the client; When sending the response message to the client by using the dedicated channel fails, feeding back a second status code to the server. 6. A data processing device for realizing a cross-domain request on a web page, wherein the device comprises: A receiving module, configured to receive a service request message initiated by a client through a webpage through a pre-deployed proxy service, the proxy service is deployed on a server with the same domain name as the webpage, and the proxy on the server The service receives the service request message through a pre-created dedicated channel; a parsing module for parsing the address variable carried in the header of the service request message; The address obtaining module is used to obtain the value of the address variable to obtain the target request address; a forwarding module, configured to forward the service request message to the server of the domain name indicated by the target request address through the proxy service; The sending module is configured to send the response message to the client through the proxy service using the dedicated channel when receiving the response message returned by the server pointed to by the target request address. 7. The data processing device for realizing cross-domain requests on a webpage according to claim 6, wherein the device further comprises: a first configuration module, configured to configure the name of the package management tool and the address of the middleware included in the service request message; a parsing unit, configured to parse the data part of the service request message through the package management tool corresponding to the name of the package management tool, to obtain the address of the middleware; The second configuration module is configured to, when the address of the middleware is the same as the address of the local end, configure the processing method after parsing the service request message to forward the requested address to the server of the domain name indicated by the parsed target request address. the service request message. 8. The data processing device for realizing cross-domain requests on a webpage according to claim 6 or 7, wherein the device further comprises an encryption module; The parsing module is further configured to parse the service data contained in the response message; The encryption module is configured to perform encryption processing on the parsed service data, and encapsulate the encrypted service data into the response message. 9. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the computer program as claimed in the claims The steps in any one of 1 to 5 of the data processing method for implementing a cross-domain request on the web page. 10. A computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, wherein, when the computer program is executed by a processor, the webpage terminal according to any one of claims 1 to 5 is implemented Steps to implement data processing methods for cross-domain requests.

Images