CN115643253A - Cross-domain file request method and device and business service system - Google Patents
Cross-domain file request method and device and business service system Download PDFInfo
- Publication number
- CN115643253A CN115643253A CN202211260734.4A CN202211260734A CN115643253A CN 115643253 A CN115643253 A CN 115643253A CN 202211260734 A CN202211260734 A CN 202211260734A CN 115643253 A CN115643253 A CN 115643253A
- Authority
- CN
- China
- Prior art keywords
- server
- file
- service
- cross
- micro
- 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
Links
Images
Abstract
The invention discloses a cross-domain file request method and device and a business service system, and relates to big data. Wherein the method comprises the following steps: receiving a file request of a user for transmitting a cross-domain file through a front page of a browser; detecting whether the browser supports a cross-domain protocol; under the condition that the browser supports a cross-domain protocol, sending a file request to a first server to access a file processing micro-service server so that the file processing micro-service server processes the file request; and under the condition that the browser does not support a cross-domain protocol, sending a file request to a second server, wherein the second server is homologous with the front-end page, the second server is connected with a plurality of micro-service servers, the plurality of micro-service servers comprise file processing micro-service servers, and the second server is used for accessing the file processing micro-service servers through a reverse proxy so as to enable the file processing micro-service servers to process the file request. The invention can improve the response speed of file processing.
Description
Technical Field
The invention relates to the technical field of big data, in particular to a cross-domain file request method and device and a business service system.
Background
This section is intended to provide a background or context to the embodiments of the invention that are recited in the claims. The description herein is not admitted to be prior art by inclusion in this section.
With the development of internet technology, users' demands for uploading and downloading of files in a network increase. When a user uploads or downloads files in a browser, the browser judges a service address to be accessed by a page, if the service address meets the same source policy, namely the protocol, the domain name and the port of the service address are consistent, the page can be directly accessed, otherwise, if the protocol, the domain name and the port of the service address are not completely consistent, the browser does not allow cross-domain access under normal conditions due to the consideration of safety.
Disclosure of Invention
The embodiment of the invention provides a cross-domain file request method, which is used for improving the response speed of file processing and comprises the following steps:
receiving a file request of a user for transmitting a cross-domain file through a front page of a browser;
detecting whether the browser supports a cross-domain protocol;
under the condition that the browser supports a cross-domain protocol, sending a file request to a first server; the first server is not homologous with the front-end page and supports a cross-domain protocol; the first server is connected with the file processing micro-service server and used for accessing the file processing micro-service server so as to enable the file processing micro-service server to process the file request; the file processing micro-service server is not homologous with the front-end page;
and under the condition that the browser does not support the cross-domain protocol, sending a file request to a second server, wherein the second server is homologous with the front-end page, the second server is connected with a plurality of micro-service servers, the plurality of micro-service servers comprise file processing micro-service servers, and the second server is used for accessing the file processing micro-service servers through a reverse proxy so that the file processing micro-service servers process the file request.
Optionally, receiving a file request of a user for transmitting a cross-domain file through a front page of a browser includes:
analyzing the service required by the operation based on the operation of the user on the front-end page;
in the case where the business service includes a file transfer service, a file request is generated.
Optionally, before receiving a file request for transmitting a cross-domain file requested by a user through a front page of a browser, the method further includes:
and adding the first server into an access address white list of the file processing micro-service server.
The embodiment of the invention also provides a cross-domain file request device, which is used for improving the response speed of file processing and comprises the following components:
the receiving unit is used for receiving a file request of a user for transmitting a cross-domain file through a front-end page request of a browser;
the detection unit is used for detecting whether the browser supports a cross-domain protocol or not;
the browser comprises a first sending unit, a second sending unit and a third sending unit, wherein the first sending unit is used for sending a file request to a first server under the condition that the browser supports a cross-domain protocol; the first server is non-homologous with the front-end page and supports a cross-domain protocol; the first server is connected with the file processing micro-service server and used for accessing the file processing micro-service server so as to enable the file processing micro-service server to process the file request; the file processing micro-service server is not homologous with the front-end page;
and the second sending unit is used for sending the file request to a second server under the condition that the browser does not support the cross-domain protocol, wherein the second server is homologous with the front-end page, the second server is connected with a plurality of micro-service servers, the plurality of micro-service servers comprise file processing micro-service servers, and the second server is used for accessing the file processing micro-service servers through a reverse proxy so as to enable the file processing micro-service servers to process the file request.
The embodiment of the invention also provides a business service system, which is used for improving the response speed of file processing and comprises the following components:
the system comprises a plurality of microservice servers, a server management server and a server management server, wherein each microservice server is used for providing corresponding microservice; the plurality of microservice servers include file processing microservice servers;
the file processing micro-service server is used for responding to the file request and accessing the file processing micro-service server so as to enable the file processing micro-service server to process the file request; the file request is a request for transmitting a cross-domain file by a user through a front page of a browser; the first server and the file processing micro-service server are not homologous with the front-end page;
the second server is connected with the micro service servers and used for receiving the file requests sent by the browser which does not support the cross-domain protocol and responding to the file requests to access the file processing micro service servers through the reverse proxy so as to enable the file processing micro service servers to process the file requests; the second server is homologous to the front-end page.
Optionally, the first server is an Apache server.
Optionally, the second server is a website Web server.
Optionally, the file handling microservice server is a Jboss server cluster.
The embodiment of the invention also provides computer equipment which comprises a memory, a processor and a computer program which is stored on the memory and can run on the processor, wherein the processor realizes the cross-domain file request method when executing the computer program.
An embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the method for requesting a cross-domain file is implemented.
An embodiment of the present invention further provides a computer program product, where the computer program product includes a computer program, and when executed by a processor, the computer program implements the cross-domain file request method described above.
In the embodiment of the invention, after receiving a file request of a user for transmitting a cross-domain file through a front-end page of a browser, whether the browser supports a cross-domain protocol is detected, if the browser supports the cross-domain protocol, the file request is sent to a first server connected with a file processing micro-service server, and the file processing micro-service server is accessed through the first server so as to process the file request, wherein the first server and the file processing micro-service server are not homologous with the front-end page, the first server supports the cross-domain protocol, and if the browser does not support the cross-domain protocol, the file request is sent to a second server homologous with the front-end page, wherein the second server is connected with a plurality of micro-service servers including the file processing micro-service server, and the second server can access the file processing micro-service server through a reverse proxy so as to enable the file processing micro-service server to process the file request.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the prior art descriptions will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and other drawings can be obtained by those skilled in the art without creative efforts. In the drawings:
fig. 1 is a schematic structural diagram of a business service system provided in an embodiment of the present invention;
fig. 2 is a schematic view of an application scenario of a service system provided in an embodiment of the present invention;
fig. 3 is a first flowchart illustrating a cross-domain file requesting method according to an embodiment of the present invention;
fig. 4 is a flowchart illustrating a cross-domain file request method according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a cross-domain file requesting device according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the embodiments of the present invention are further described in detail below with reference to the accompanying drawings. The exemplary embodiments and descriptions of the present invention are provided to explain the present invention, but not to limit the present invention.
In the embodiment of the present invention, a business service system is provided, as shown in fig. 1, the business service system includes a plurality of microservice servers 50, a first server 51 and a second server 52, where the plurality of microservice servers includes a file processing microservice server 501 and another microservice server 502.
Each of the plurality of microservice servers 50 is configured to provide a corresponding microservice, for example, the file processing microservice server 501 is configured to provide a file processing service, and each of the other microservice servers 502 may also provide a corresponding microservice, which is not described herein again. Alternatively, the file processing microservice server 501 may be a Jboss server cluster.
The architecture of the microservice is a variant of a software development technology-Service Oriented Architecture (SOA) architecture style, and the architecture divides a single application program into a group of small services, each service is a microservice, and the microservices are mutually coordinated and matched to provide final services for users. Each microservice is built around a specific business service and can be deployed independently to a production environment, a production-like environment, etc., can run in its independent process.
The first server 51 is connected to a file handling microservice server 501, which may be a network connection. The servers may be accessible to each other via a network connection. The first server 51 is configured to receive a file request sent by a browser supporting a cross-domain protocol, and access the file processing micro-service server 501 in response to the file request, so that the file processing micro-service server 501 processes the file request, where the file request is a request of a user to transmit a cross-domain file through a front-end page of the browser. The front-end page is a page that a user sees in a browser and can complete various service requests required by the business function.
The first server 51 and the file processing microservice server 501 are non-homogeneous with the front-end pages. The front-end page is provided by a website, the non-homologous is that a protocol, a domain name and a port of the address of the website of the front-end page are not completely consistent, and when the browser finds that a service address required to be accessed by the same page is non-homologous (namely, the service address does not accord with a homologous policy), the browser does not allow direct cross-domain access due to the consideration of safety. However, in the case where the browser supports the cross-domain protocol, it may be connected to a server that also supports the cross-domain protocol. The Cross-domain protocol may be a Cross-Origin Resource Sharing (CORS) protocol.
Therefore, in the embodiment of the present invention, the first server 51 supports the cross-domain protocol, so that, in the case that the browser also supports the cross-domain protocol, the front-end page may configure the file request to be sent to the first server 51, so as to issue the file request of a non-homologous source. After the first server 51 receives the file request, the file processing microservice server 501 may be accessed to process the file request. The file request is used to request the transfer (upload or download) of a cross-domain file. Alternatively, the first server 51 may be an Apache server.
The second server 52 is connected to the plurality of microservice servers 50, and is configured to receive a file request sent by a browser that does not support a cross-domain protocol, and to access the file processing microservice server 501 through a reverse proxy in response to the file request, so that the file processing microservice server 501 processes the file request, and the second server 52 is homologous to the front-end page. The servers are not restricted to being homologous, and are accessible by a network connection or configuration agent, so that the second server 52 can be accessed even though it is not homologous to the file processing microservice server 501. Alternatively, the second server 52 may be a Web server.
An implementation manner of the service system provided by the embodiment of the present invention in an application scenario is shown in fig. 2. Digital bank public services such as batch account transfer, payroll sending, report downloading and the like all relate to uploading and downloading of files, and a large amount of file transmission needs to occupy a large amount of service bandwidth, so that normal execution of other requests is possibly influenced. For the service system shown in fig. 2, before application, a file request server (first server) and a file processing microservice server are networked, a Web front-end server (second server) is newly added to the proxy configuration of the file processing microservice server, the address configuration of the file request server is newly added in the front-end project, the file processing microservice server is set to support the CORS protocol, the file request server is added into an address white list, a judgment whether a currently used browser supports the CORS protocol is newly added in the front-end project, the file requests the Web front-end server address for the browser which does not support the CORS protocol, otherwise, the file request server is requested.
As shown in fig. 2, a user may access a front-end page of a service through a browser, and when the user issues a service request in an operation executed by the front-end page, the service request may include a file request for requesting uploading or downloading of a file, and at this time, if the browser supports the CORS cross-domain protocol, the browser may request a file request server (apache server) that is not homologous to the front-end page but also supports the CORS cross-domain protocol, and the file request server may directly access the file processing microservice server through a network connection, and if the browser does not support the CORS cross-domain protocol, the browser requests a Web front-end server that is homologous to the front-end page, and the server is a front-end server, and is connected to microservice servers of a plurality of service modules, including a transfer module microservice server, a wage microservice server, and other module microservice servers, and accesses the file processing microservice server through a reverse proxy, so that the Web front-end server may access the file processing microservice server in a reverse direction after receiving the file request of the browser. The embodiment of the invention can decouple the request of the file service from other Web service requests, and processes the file request by independently setting the file processing micro-service server for processing the file request, thereby greatly reducing the bandwidth pressure of other Web service requests, not only splitting the bandwidth of different requests, but also ensuring a larger compatible range of a browser.
In the embodiment of the invention, after receiving a file request of a user for transmitting a cross-domain file through a front-end page of a browser, whether the browser supports a cross-domain protocol is detected, if the browser supports the cross-domain protocol, the file request is sent to a first server connected with a file processing micro-service server, and the file processing micro-service server is accessed through the first server so as to process the file request, wherein the first server and the file processing micro-service server are not homologous with the front-end page, the first server supports the cross-domain protocol, and if the browser does not support the cross-domain protocol, the file request is sent to a second server homologous with the front-end page, wherein the second server is connected with a plurality of micro-service servers including the file processing micro-service server, the second server can access the file processing micro-service server through a reverse proxy so as to enable the file processing micro-service server to process the file request.
An embodiment of the present invention provides a cross-domain file request method, and fig. 3 is a schematic flowchart illustration of a cross-domain file request method according to an embodiment of the present invention. As shown in fig. 3, the method may include the steps of:
The user can open a browser through electronic equipment such as a mobile phone and a computer and access a front-end page providing business service. The user can send a request through a specified operation, such as clicking a button of a certain service function, the front-end page can analyze the request through a script, each micro service required by the service function is analyzed, and when the user needs to request transmission (transmission comprises uploading and downloading) of a cross-domain file, the user sends a file request.
The script of the front-end page is written in advance to detect whether the browser supports the cross-domain protocol after receiving the file request, if the browser is determined to support the cross-domain protocol, step 103 is executed, otherwise step 104 is executed.
And 103, sending a file request to the first server under the condition that the browser supports the cross-domain protocol. The first server is non-homologous with the front-end page and supports a cross-domain protocol; the first server is connected with the file processing micro-service server and used for accessing the file processing micro-service server so as to enable the file processing micro-service server to process the file request; the file handling microservice server is non-homogeneous with the front-end page.
And 104, sending a file request to a second server under the condition that the browser does not support the cross-domain protocol. The second server is homologous with the front-end page, the second server is connected with the micro-service servers, the micro-service servers comprise file processing micro-service servers, and the second server is used for accessing the file processing micro-service servers through a reverse proxy so that the file processing micro-service servers process file requests.
Step 103 and step 104 may refer to the description of the business service system for processing the file request as shown in fig. 1 and fig. 2, and are not described herein again.
Alternatively, the step of receiving a file request for transmitting the cross-domain file requested by the user through the front page of the browser may include the following steps as shown in fig. 4:
The file handling microservice server may be configured to allow access by the first server by adding the first server to the access address whitelist of the file handling microservice server prior to receiving a file request from a user to transfer a cross-domain file via a front-end page of a browser.
In the embodiment of the invention, after receiving a file request of a user for transmitting a cross-domain file through a front-end page of a browser, whether the browser supports a cross-domain protocol is detected, if the browser supports the cross-domain protocol, the file request is sent to a first server connected with a file processing micro-service server, and the file processing micro-service server is accessed through the first server so as to process the file request, wherein the first server and the file processing micro-service server are not homologous with the front-end page, the first server supports the cross-domain protocol, and if the browser does not support the cross-domain protocol, the file request is sent to a second server homologous with the front-end page, wherein the second server is connected with a plurality of micro-service servers including the file processing micro-service server, the second server can access the file processing micro-service server through a reverse proxy so as to enable the file processing micro-service server to process the file request.
The embodiment of the invention also provides a cross-domain file request device, which is described in the following embodiments. Because the problems and the principle solved by the device are similar to those of the cross-domain file request method provided by the embodiment of the invention, the implementation of the device can refer to the implementation of the cross-domain file request method, and repeated parts are not described again.
Fig. 5 is a schematic structural diagram of a cross-domain file requesting device according to an embodiment of the present invention, and as shown in fig. 5, the device includes a receiving unit 10, a detecting unit 20, a first sending unit 30, and a second sending unit 40.
The receiving unit 10 is configured to receive a file request of a user requesting to transmit a cross-domain file through a front-end page of a browser; the detecting unit 20 is configured to detect whether the browser supports a cross-domain protocol; the first sending unit 30 is configured to send a file request to the first server when the browser supports a cross-domain protocol; the first server is non-homologous with the front-end page and supports a cross-domain protocol; the first server is connected with the file processing micro-service server and used for accessing the file processing micro-service server so as to enable the file processing micro-service server to process the file request; the file processing micro-service server is not homologous with the front-end page; the second sending unit 40 is configured to send a file request to a second server in a case where the browser does not support the cross-domain protocol, where the second server is homologous to the front-end page, the second server is connected to a plurality of micro-service servers, the plurality of micro-service servers include a file processing micro-service server, and the second server is configured to access the file processing micro-service server through a reverse proxy so that the file processing micro-service server processes the file request.
In the embodiment of the invention, after receiving a file request of a user for transmitting a cross-domain file through a front-end page of a browser, whether the browser supports a cross-domain protocol is detected, if the browser supports the cross-domain protocol, the file request is sent to a first server connected with a file processing micro-service server, and the file processing micro-service server is accessed through the first server so as to process the file request, wherein the first server and the file processing micro-service server are not homologous with the front-end page, the first server supports the cross-domain protocol, and if the browser does not support the cross-domain protocol, the file request is sent to a second server homologous with the front-end page, wherein the second server is connected with a plurality of micro-service servers including the file processing micro-service server, the second server can access the file processing micro-service server through a reverse proxy so as to enable the file processing micro-service server to process the file request.
The embodiment of the invention also provides computer equipment which comprises a memory, a processor and a computer program which is stored on the memory and can run on the processor, wherein the processor realizes the cross-domain file request method when executing the computer program.
An embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the method for requesting a cross-domain file is implemented.
An embodiment of the present invention further provides a computer program product, where the computer program product includes a computer program, and when executed by a processor, the computer program implements the cross-domain file request method described above.
In the embodiment of the invention, after receiving a file request of a user for transmitting a cross-domain file through a front-end page of a browser, whether the browser supports a cross-domain protocol is detected, if the browser supports the cross-domain protocol, the file request is sent to a first server connected with a file processing micro-service server, and the file processing micro-service server is accessed through the first server so as to process the file request, wherein the first server and the file processing micro-service server are not homologous with the front-end page, the first server supports the cross-domain protocol, and if the browser does not support the cross-domain protocol, the file request is sent to a second server homologous with the front-end page, wherein the second server is connected with a plurality of micro-service servers including the file processing micro-service server, the second server can access the file processing micro-service server through a reverse proxy so as to enable the file processing micro-service server to process the file request.
According to the technical scheme, the data acquisition, storage, use, processing and the like meet relevant regulations of national laws and regulations, and various types of data such as personal identity data, operation data, behavior data and the like related to individuals, clients, crowds and the like are authorized.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The above-mentioned embodiments are intended to illustrate the objects, technical solutions and advantages of the present invention in further detail, and it should be understood that the above-mentioned embodiments are only exemplary embodiments of the present invention, and are not intended to limit the scope of the present invention, and any modifications, equivalent substitutions, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.
Claims (11)
1. A cross-domain file request method is characterized by comprising the following steps:
receiving a file request of a user for transmitting a cross-domain file through a front page of a browser;
detecting whether the browser supports a cross-domain protocol;
sending the file request to a first server if the browser supports the cross-domain protocol; wherein the first server is non-homogeneous with the front-end page and supports the cross-domain protocol; the first server is connected with the file processing micro-service server and used for accessing the file processing micro-service server so as to enable the file processing micro-service server to process the file request; the file processing microservice server is non-homologous to the front-end page;
and sending the file request to a second server under the condition that the browser does not support the cross-domain protocol, wherein the second server is homologous with the front-end page, the second server is connected with a plurality of micro-service servers, the micro-service servers comprise the file processing micro-service server, and the second server is used for accessing the file processing micro-service server through a reverse proxy so as to enable the file processing micro-service server to process the file request.
2. The method of claim 1, wherein receiving a file request from a user to transfer a cross-domain file via a front-end page of a browser comprises:
analyzing the business service required by the operation based on the operation of the user on the front-end page;
and generating the file request under the condition that the business service comprises a file transmission service.
3. The method of claim 1, prior to receiving a file request from a user to transfer a cross-domain file via a front-end page of a browser, further comprising:
and adding the first server into an access address white list of the file processing micro-service server.
4. A cross-domain file requesting apparatus, comprising:
the receiving unit is used for receiving a file request of a user for transmitting a cross-domain file through a front-end page request of a browser;
the detection unit is used for detecting whether the browser supports a cross-domain protocol or not;
a first sending unit, configured to send the file request to a first server when the browser supports the cross-domain protocol; wherein the first server is non-homogeneous with the front-end page and supports the cross-domain protocol; the first server is connected with the file processing micro-service server and used for accessing the file processing micro-service server so as to enable the file processing micro-service server to process the file request; the file processing microservice server is non-homologous to the front-end page;
a second sending unit, configured to send the file request to a second server when the browser does not support the cross-domain protocol, where the second server is homologous to the front-end page, the second server is connected to a plurality of micro-service servers, the plurality of micro-service servers include the file processing micro-service server, and the second server is configured to access the file processing micro-service server through a reverse proxy, so that the file processing micro-service server processes the file request.
5. A business service system, comprising:
the system comprises a plurality of micro-service servers, a server management server and a server management server, wherein each micro-service server is used for providing a corresponding micro-service; the plurality of microservice servers include file processing microservice servers;
the first server is connected with the file processing micro-service server and used for receiving a file request sent by a browser supporting a cross-domain protocol and responding to the file request to access the file processing micro-service server so as to enable the file processing micro-service server to process the file request; the file request is a request for transmitting a cross-domain file by a user through a front-end page of the browser; the first server and the file processing microservice server are non-homologous to the front-end page;
the second server is connected with the micro service servers and used for receiving file requests sent by browsers which do not support the cross-domain protocol and responding to the file requests to access the file processing micro service servers through reverse proxies so that the file processing micro service servers process the file requests; the second server is homologous to the front-end page.
6. The system of claim 5, wherein the first server is an Apache server.
7. The system of claim 5, wherein the second server is a Web server.
8. The system of claim 5 wherein the file processing microservice server is a Jboss server cluster.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method of any one of claims 1 to 3 when executing the computer program.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program which, when executed by a processor, implements the method of any one of claims 1 to 3.
11. A computer program product, characterized in that the computer program product comprises a computer program which, when being executed by a processor, carries out the method of any one of claims 1 to 3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211260734.4A CN115643253A (en) | 2022-10-14 | 2022-10-14 | Cross-domain file request method and device and business service system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211260734.4A CN115643253A (en) | 2022-10-14 | 2022-10-14 | Cross-domain file request method and device and business service system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115643253A true CN115643253A (en) | 2023-01-24 |
Family
ID=84944809
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211260734.4A Pending CN115643253A (en) | 2022-10-14 | 2022-10-14 | Cross-domain file request method and device and business service system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115643253A (en) |
-
2022
- 2022-10-14 CN CN202211260734.4A patent/CN115643253A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20210289045A1 (en) | Offline client replay and sync | |
| WO2016101635A1 (en) | Method, apparatus and device for synchronizing login status, and computer storage medium | |
| US20150128121A1 (en) | Dynamic application version selection | |
| US11436066B2 (en) | System for offline object based storage and mocking of rest responses | |
| CN107463453B (en) | Method, device, equipment and storage medium for communication between different applications of same terminal | |
| CN109542862B (en) | Method, device and system for controlling mounting of file system | |
| CN111262839A (en) | Vulnerability scanning method, management equipment, node and storage medium | |
| CN108737471B (en) | Network access method and device | |
| US20200192732A1 (en) | Predictive Microservice Systems and Methods | |
| CN112261111A (en) | Method and system for realizing cross-domain access of browser in application program | |
| US20210067550A1 (en) | Method and apparatus for distributed emulation of behavior of a malicious domain | |
| CN114285659A (en) | Reverse proxy method, device, equipment and storage medium | |
| CN111600755B (en) | Internet access behavior management system and method | |
| US9998559B2 (en) | Preemptive caching of data | |
| US20170111430A1 (en) | Methods for website version control using bucket cookies | |
| WO2017036042A1 (en) | Information collection method and apparatus | |
| US10771578B2 (en) | Webpage loading method and apparatus | |
| CN111552643A (en) | Multi-browser webpage access synchronization method and system | |
| JP6199844B2 (en) | Suspicious part estimation device and suspected part estimation method | |
| CN108810070B (en) | Resource sharing method and device, intelligent equipment and storage medium | |
| US10044728B1 (en) | Endpoint segregation to prevent scripting attacks | |
| CN114124883B (en) | Data access method and device based on cloud storage address, computer equipment and medium | |
| CN115643253A (en) | Cross-domain file request method and device and business service system | |
| CN114915565A (en) | Method and system for debugging network | |
| CN109302446B (en) | Cross-platform access method and device, electronic equipment and storage medium |
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 |