CN111435380B - Page cross-domain interaction method, system, device and storage device - Google Patents
Page cross-domain interaction method, system, device and storage device Download PDFInfo
- Publication number
- CN111435380B CN111435380B CN201910032143.3A CN201910032143A CN111435380B CN 111435380 B CN111435380 B CN 111435380B CN 201910032143 A CN201910032143 A CN 201910032143A CN 111435380 B CN111435380 B CN 111435380B
- Authority
- CN
- China
- Prior art keywords
- data
- domain page
- processed
- page
- domain
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 40
- 230000003993 interaction Effects 0.000 title claims abstract description 27
- 238000004590 computer program Methods 0.000 claims description 11
- 230000001960 triggered effect Effects 0.000 claims description 4
- 230000005540 biological transmission Effects 0.000 abstract description 9
- 238000010586 diagram Methods 0.000 description 8
- 230000006870 function Effects 0.000 description 6
- 238000004891 communication Methods 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 238000012545 processing Methods 0.000 description 3
- 238000012546 transfer Methods 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- BSFODEXXVBBYOC-UHFFFAOYSA-N 8-[4-(dimethylamino)butan-2-ylamino]quinolin-6-ol Chemical compound C1=CN=C2C(NC(CCN(C)C)C)=CC(O)=CC2=C1 BSFODEXXVBBYOC-UHFFFAOYSA-N 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 210000001503 joint Anatomy 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
The application discloses a page cross-domain interaction method, a system, equipment and a storage medium. The method comprises the following steps: the method comprises the steps that a second domain page receives an access request of a second domain page sent by a user in a first domain page, wherein the access request comprises a Uniform Resource Locator (URL) of the second domain page, and the URL carries an identifier of data to be processed in the first domain page; analyzing the access request to obtain the identification of the data to be processed; the identification of the data to be processed is sent to the server of the second domain page, so that the server of the second domain page obtains the data to be processed from the server of the first domain page according to the identification of the data to be processed; and receiving and displaying the data to be processed sent by the server of the second domain page. According to the technical scheme of the embodiment of the application, data transmission between cross-domain pages can be realized.
Description
Technical Field
The present disclosure relates generally to the field of computer technology, and in particular, to the field of information interaction technology, and in particular, to a method, a system, a device, and a storage device for page cross-domain interaction.
Background
In the background management system, in order to facilitate the operation of a user, improve the working efficiency, reduce the cost of switching between different systems of the user, and embed other system pages for use. In the case of associating the embedded page with the main page, a data transmission problem is inevitably involved, and a GET request method of hypertext transfer protocol (HTTP, hyper Text Transfer Protocol) is generally adopted, however, in consideration of security and size limitation of data transmission, a POST request method of HTTP has to be selected. However, a problem of cross-domain occurs because it is a front-end page that requests another system across systems.
Therefore, how to solve the cross-domain problem and realize data transmission between different system pages is a problem to be solved.
Disclosure of Invention
In view of the foregoing drawbacks or shortcomings in the prior art, it is desirable to provide a scheme that enables data transfer between cross-domain pages.
In a first aspect, an embodiment of the present application provides a method for page cross-domain interaction, including:
the method comprises the steps that a second domain page receives an access request of a second domain page sent by a user in a first domain page, wherein the access request comprises a Uniform Resource Locator (URL) of the second domain page, and the URL carries an identifier of data to be processed in the first domain page;
analyzing the access request to obtain the identification of the data to be processed;
the identification of the data to be processed is sent to the server of the second domain page, so that the server of the second domain page obtains the data to be processed from the server of the first domain page according to the identification of the data to be processed;
and receiving and displaying the data to be processed sent by the server of the second domain page.
In a second aspect, an embodiment of the present application further provides a page cross-domain interaction system, including: the server comprises a first domain page, a server of the first domain page, a second domain page and a server of the second domain page, wherein:
the second domain page is configured to receive an access request of the second domain page sent by a user on the first domain page, where the access request includes a URL of the second domain page, and the URL carries an identifier of data to be processed in the first domain page; analyzing the access request to obtain the identification of the data to be processed, and sending the identification to a server of the second domain page; receiving and displaying the data to be processed sent by the server of the second domain page;
and the server of the second domain page is used for acquiring the data to be processed from the server of the first domain page according to the identification of the data to be processed.
In a third aspect, embodiments of the present application further provide an apparatus, including: at least one processor, at least one memory, and computer program instructions stored in the memory that when executed by the processor implement the page-crossing interaction method as described above.
In a fourth aspect, embodiments of the present application also provide a computer readable storage medium having stored thereon computer program instructions which, when executed by a processor, implement a page-crossing interaction method as described above.
According to the page cross-domain interaction scheme provided by the embodiment of the invention, an access request is sent to a second domain page through a first domain page, the access request comprises the URL of the second domain page carrying the identification of the data to be processed in the first domain page, the second domain page analyzes the access request, the identification of the data to be processed is obtained and then sent to a server of the second domain page, so that the server of the second domain page can acquire the data to be processed from the server of the first domain page according to the identification of the data to be processed and feed back the data to be processed to the second domain page, and the second domain page displays the received data to be processed. According to the technical scheme, the cross-domain problem caused by data transmission and interaction among a plurality of system pages is solved by adopting a front-end page-back-end server request mode.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the detailed description of non-limiting embodiments, made with reference to the following drawings, in which:
FIG. 1 illustrates an exemplary flowchart of a method for page cross-domain interaction provided by an embodiment of the present application;
FIG. 2 illustrates an exemplary flowchart of a method of page cross-domain interaction provided by an embodiment of the present application;
FIG. 3 illustrates an exemplary block diagram of a page cross-domain interaction system provided by an embodiment of the present application; and
FIG. 4 illustrates a schematic diagram of a computer system suitable for use in implementing embodiments of the present application.
Detailed Description
The present application is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be noted that, for convenience of description, only the portions related to the invention are shown in the drawings.
It should be noted that, in the case of no conflict, the embodiments and features in the embodiments may be combined with each other.
As mentioned in the background art, in the background management system, in order to facilitate the operation of a user, improve the working efficiency, reduce the cost of switching between different systems for the user, and embed other system pages for use. When the association operation is performed between the embedded page and the main page, a problem of data transmission is inevitably involved. However, a problem of cross-domain occurs because it is a front-end page that requests another system across systems.
In view of the above-mentioned drawbacks of the prior art, the present embodiment provides a page cross-domain interaction scheme, where an access request is sent to a second domain page through a first domain page, where the access request includes a URL of the second domain page carrying an identifier of data to be processed in the first domain page, the second domain page parses the access request, obtains the identifier of the data to be processed, and sends the identifier to a server of the second domain page, so that the server of the second domain page can obtain the data to be processed from the server of the first domain page according to the identifier of the data to be processed and feed back the data to be processed to the second domain page, where the second domain page displays the received data to be processed. According to the technical scheme, the cross-domain problem caused by data transmission and interaction among a plurality of system pages is solved by adopting a front-end page-back-end server request mode.
The page cross-domain method provided by the embodiment of the application can be embedded into mobile terminals such as WeChat public numbers, weChat applets, payment device life numbers, APP and the like, and multi-terminals such as a computer browser HTML5 and the like. In the scenario that front-end pages of multiple systems are embedded into each other (the front-end pages are uniformly logged in to have authority), a user can use page functions and data of the systems with one system as a fulcrum and without switching the systems.
The method of the embodiments of the present application will be described below in conjunction with flowcharts.
Referring to fig. 1, an exemplary flowchart of a page cross-domain interaction method provided in an embodiment of the present application is shown.
The method comprises the following steps:
step 110, the second domain page receives an access request of the second domain page sent by the user on the first domain page, where the access request includes a uniform resource locator (Uniform Resource Locator, URL) of the second domain page, and the URL carries an identifier of data to be processed in the first domain page.
In this embodiment, when a user operates service data on a first domain page, the service data needs to be synchronously processed on a second domain page due to service reasons, and at this time, the user may call the second domain page on the first domain page and send an access request to the second domain page, where the access request needs to carry a URL of the second domain page and meanwhile carries an identifier of data to be processed, where the data to be processed refers to the service data that needs to be synchronously processed on the second domain page.
And 120, analyzing the access request by the second domain page to obtain the identification of the data to be processed.
Specifically, after the second domain page receives the access request, the identifier of the data to be processed carried by the second domain page is parsed from the URL in the access request.
And 130, sending the identification of the data to be processed to a server of the second domain page, so that the server of the second domain page obtains the data to be processed from the server of the first domain page according to the identification of the data to be processed.
Specifically, the second domain page sends the identification of the data to be processed to a server of the second domain page;
after the server of the second domain page receives the identification of the data to be processed, the identification of the data to be processed can be sent to the server of the first domain page in a POST request mode;
the server of the first domain page searches the data to be processed corresponding to the identification of the data to be processed from the database of the server according to the identification of the data to be processed, and sends the searched data to be processed to the server of the second domain page.
And 140, receiving and displaying the data to be processed sent by the server of the second domain page.
Optionally, when the first domain page sends an access request to the second domain page, the URL included in the access request may further carry a first domain page identifier, where the first domain page identifier is used to characterize a data source.
Thus, after the second domain page parses the parameters (including the identifier of the data to be processed and the identifier of the first domain page) in the URL from the access request and sends the parameters to the server of the second domain page, the server of the second domain page may determine the data source according to the identifier of the first domain page, and then send the identifier of the data to be processed to the determined data source, that is, the server of the first domain page, so as to obtain the data to be processed.
Optionally, the URL included in the access request may further carry an identifier of all data in the first domain page and a current data index.
When the second domain page analyzes parameters (including the identification of the data to be processed, the identification of all the data in the first domain page and the current data index) in the URL from the access request and the second domain page receives an operation request of the last or the next piece of data to be processed, which is triggered by a user, the identification of the new data to be processed is determined according to the identification of all the data in the first domain page and the current data index, and the identification of the new data to be processed is sent to the server of the second domain page, so that the server of the second domain page obtains the new data to be processed from the server of the first domain page according to the identification of the new data to be processed.
According to the page cross-domain interaction scheme provided by the embodiment of the invention, an access request is sent to a second domain page through a first domain page, the access request comprises the URL of the second domain page carrying the identification of the data to be processed in the first domain page, the second domain page analyzes the access request, the identification of the data to be processed is obtained and then sent to a server of the second domain page, so that the server of the second domain page can acquire the data to be processed from the server of the first domain page according to the identification of the data to be processed and feed back the data to be processed to the second domain page, and the second domain page displays the received data to be processed. According to the technical scheme, the cross-domain problem caused by data transmission and interaction among a plurality of system pages is solved by adopting a front-end page-back-end server request mode.
The method for page cross-domain interaction provided in the embodiment of the present application will be described in detail below with reference to a flowchart, as shown in fig. 2, which is a schematic flowchart of the method for page cross-domain interaction provided in the embodiment of the present application. The method is applied to a scene that the system A and the system B are mutually nested. The method comprises the following steps:
in step 210, the user clicks on the front page of the system a and sends an access request to the front page of the system B.
The access request may be sent by a GET request manner, where the following parameters are carried in the URL of the front page of the system B to be sent:
1. all data identification of front page of system a (id 1, id2,..and idn)
2. Current data index (index NUm: id) for front page of System A
3. Identification of pending data for front page of System A (SelectedId: id)
4. Data source identifier (sourceFrom)
Assembling the parameters, the obtained URL may be, for example:
"http://127.0.0.1:8000/static/B.htmlcdmData＝{"indexNUm":0,"sele ctedId":"37","dataList":[{"id":"37"},{"id":"43045"}],"sourceFrom":"listP age"}"
and 220, analyzing the received access request by the front-end page of the system B to obtain all data identifiers, the current data index, the identifiers of the data to be processed and the data source identifiers of the front-end page of the system A carried in the access request, and sending the identifiers of the data to be processed to a back-end server of the system B.
In step 230, the backend server of the system B sends the identifier of the data to be processed to the backend server of the system a in a POST request manner.
And 240, the back-end server of the system A returns the data to be processed to the back-end server of the system B according to the identification of the data to be processed.
Specifically, the back-end server of the system A searches the data to be processed corresponding to the identification of the data to be processed from the database of the back-end server according to the identification of the data to be processed, and sends the searched data to be processed to the back-end server of the system B.
And 250, the back-end server of the system B returns the received data to be processed to the front-end page of the system B, and the front-end page of the system B performs rendering loading on the data to be processed to complete user association operation.
By adopting the page cross-domain interaction scheme provided by the embodiment of the application, the following technical effects can be achieved:
1. the method can realize seamless butt joint among the pages of the multiple systems, improve the diversity of the systems, enhance the user experience and reduce the cost of switching back and forth among the multiple systems.
2. And realizing batch data transmission under a scene of mutually nesting cross-system pages.
3. The cost increased by repeated page development is reduced.
It should be noted that although the operations of the method of the present invention are depicted in the drawings in a particular order, this does not require or imply that the operations must be performed in that particular order or that all of the illustrated operations be performed in order to achieve desirable results. Rather, the steps depicted in the flowcharts may change the order of execution. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step to perform, and/or one step decomposed into multiple steps to perform.
With further reference to FIG. 3, an exemplary block diagram of a structure providing a page cross-domain interaction system is shown in accordance with an embodiment of the present application.
The system comprises a first domain page 31, a server 32 of the first domain page, a second domain page 33 and a server 34 of the second domain page, wherein:
the second domain page 33 is configured to receive an access request of the second domain page 33 sent by the user on the first domain page 31, where the access request includes a URL of the second domain page 33, and the URL carries an identifier of data to be processed in the first domain page 31; analyzing the access request to obtain the identification of the data to be processed, and sending the identification to the server 34 of the second domain page; receiving and displaying the data to be processed sent by the server 34 of the second domain page;
the server 34 of the second domain page is configured to obtain the data to be processed from the server 32 of the first domain page according to the identification of the data to be processed.
Optionally, the server 34 of the second domain page is specifically configured to:
sending the identification of the data to be processed to the server 32 of the first domain page; and receives the data to be processed sent by the server 32 of the first domain page;
the server 32 of the first domain page is configured to:
and searching the data to be processed corresponding to the identification of the data to be processed from the database of the server 34 according to the identification of the data to be processed, and sending the searched data to be processed to the server of the second domain page.
The URL also carries a first domain page identifier; then
The second domain page 33 is further configured to:
analyzing the access request to obtain the first domain page identifier, and sending the first domain page identifier to the server 34 of the second domain page;
the server 34 of the second domain page is specifically configured to:
and according to the first domain page identifier, sending the identifier of the data to be processed to a server 32 of the first domain page corresponding to the first domain page identifier.
Optionally, the URL further carries an identifier of all data in the first domain page and a current data index; then
The second domain page 33 is further configured to:
analyzing the access request to obtain the identifiers and the current data indexes of all data in the first domain page 31; when an operation request of the last or the next data of the data to be processed triggered by a user is received, determining the identification of new data to be processed according to the identifications and the current data indexes of all the data in the first domain page 31, and sending the identification of the new data to be processed to the server 34 of the second domain page;
the server 34 of the second domain page is further configured to:
and acquiring the new data to be processed from the server 32 of the first domain page according to the identification of the new data to be processed.
It should be understood that the subsystems or units described in the system correspond to the various steps in the method described with reference to fig. 1 and 2. Thus, the operations and features described above for the method are equally applicable to the system and the units contained therein, and are not described in detail herein.
Referring now to FIG. 4, there is illustrated a schematic diagram of a computer system 400 suitable for use in implementing a server of an embodiment of the present application.
As shown in fig. 4, the computer system includes a Central Processing Unit (CPU) 401, which can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 402 or a program loaded from a storage section into a Random Access Memory (RAM) 403. In the RAM403, various programs and data required for the system operation are also stored. The CPU 401, ROM 402, and RAM403 are connected to each other by a bus 404. An input/output (I/O) interface 405 is also connected to bus 404.
The following components are connected to the I/O interface 405: an input section 406 including a keyboard, a mouse, and the like; an output section including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), etc., and a speaker, etc.; a storage section 408 including a hard disk or the like; and a communication section 409 including a network interface card such as a LAN card, a modem, or the like. The communication section 409 performs communication processing via a network such as the internet. The drives are also connected to the I/O interface 405 as needed. A removable medium 411 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is installed on the drive 410 as needed, so that a computer program read therefrom is installed into the storage section 408 as needed.
In particular, the processes described above with reference to flowcharts 1-2 may be implemented as computer software programs according to embodiments of the present invention. For example, embodiments of the present invention include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flowcharts. In such embodiments, the computer program may be downloaded and installed from a network via a communication portion, and/or installed from a removable medium. The above-described functions defined in the system of the present application are performed when the computer program is executed by a Central Processing Unit (CPU) 401.
The computer readable medium shown in the present invention may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units involved in the embodiments of the present invention may be implemented by software, or may be implemented by hardware, and the described units may also be provided in a processor. Wherein the names of the units do not constitute a limitation of the units themselves in some cases. The described units or modules may also be provided in a processor.
As another aspect, the present application also provides a computer-readable medium that may be contained in the electronic device described in the above embodiment; or may exist alone without being incorporated into the electronic device. The computer readable medium carries one or more programs which, when executed by one of the electronic devices, cause the electronic device to implement the page-crossing interaction method as described in the above embodiments.
It should be noted that although in the above detailed description several modules or units of a device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit in accordance with embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into a plurality of modules or units to be embodied.
Furthermore, although the steps of the methods in the present disclosure are depicted in a particular order in the drawings, this does not require or imply that the steps must be performed in that particular order or that all illustrated steps be performed in order to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step to perform, and/or one step decomposed into multiple steps to perform, etc.
From the above description of embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or may be implemented in software in combination with the necessary hardware.
Claims (6)
1. A method of page cross-domain interaction, the method comprising:
the method comprises the steps that a second domain page receives an access request of a second domain page sent by a user in a first domain page, wherein the access request comprises a Uniform Resource Locator (URL) of the second domain page, and the URL carries an identification of data to be processed in the first domain page, an identification of all data in the first domain page and a current data index;
analyzing the access request to obtain the identification of the data to be processed;
the second domain page sends the identification of the data to be processed to a server of the second domain page;
the server of the second domain page sends the identification of the data to be processed to the server of the first domain page;
the server of the first domain page searches the data to be processed corresponding to the identification of the data to be processed from a database of the server according to the identification of the data to be processed, and sends the searched data to be processed to the server of the second domain page;
receiving and displaying the data to be processed sent by the server of the second domain page;
the second domain page analyzes the access request to obtain identifiers and current data indexes of all data in the first domain page;
when the second domain page receives an operation request of the last data or the next data of the data to be processed, which is triggered by a user, determining the identification of new data to be processed according to the identifications of all data in the first domain page and the current data index, and sending the identification of the new data to be processed to a server of the second domain page, so that the server of the second domain page obtains the new data to be processed from the server of the first domain page according to the identification of the new data to be processed.
2. The method of claim 1, wherein the URL further carries a first domain page identifier; then
The method further comprises the steps of:
the second domain page analyzes the access request to obtain the first domain page identifier, and sends the first domain page identifier to a server of the second domain page; and
the server of the second domain page sends the identification of the data to be processed to the server of the first domain page, and the method comprises the following steps:
and the server of the second domain page sends the identification of the data to be processed to the server of the first domain page corresponding to the first domain page identification according to the first domain page identification.
3. A page cross-domain interaction system, the system comprising a first domain page, a server for the first domain page, a second domain page, and a server for the second domain page, wherein:
the second domain page is configured to receive an access request of the second domain page sent by a user on the first domain page, where the access request includes a URL of the second domain page, and the URL carries an identifier of data to be processed in the first domain page, an identifier of all data in the first domain page, and a current data index; analyzing the access request to obtain the identification of the data to be processed, and sending the identification to a server of the second domain page; receiving and displaying the data to be processed sent by the server of the second domain page;
the server of the first domain page is used for searching the data to be processed corresponding to the identification of the data to be processed from the database of the server according to the identification of the data to be processed, and sending the searched data to be processed to the server of the second domain page;
the server of the second domain page is used for sending the identification of the data to be processed to the server of the first domain page, receiving the data to be processed sent by the server of the first domain page, and acquiring the new data to be processed from the server of the first domain page according to the identification of the new data to be processed;
wherein the second domain page is further configured to:
analyzing the access request to obtain the identifications and the current data indexes of all data in the first domain page; when an operation request of the last or the next data of the data to be processed, which is triggered by a user, is received, determining the identification of the new data to be processed according to the identifications of all the data in the first domain page and the current data index, and sending the identification of the new data to be processed to a server of the second domain page.
4. The system of claim 3, wherein the URL further carries a first domain page identifier; then
The second domain page is further configured to:
analyzing the access request to obtain the first domain page identifier, and sending the first domain page identifier to a server of the second domain page;
the server of the second domain page is specifically configured to:
and according to the first domain page identification, sending the identification of the data to be processed to a server of a first domain page corresponding to the first domain page identification.
5. A page cross-domain interaction device, comprising: at least one processor, at least one memory, and computer program instructions stored in the memory, which when executed by the processor, implement the method of any one of claims 1-2.
6. A computer readable storage medium having stored thereon computer program instructions, which when executed by a processor, implement the method of any of claims 1-2.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910032143.3A CN111435380B (en) | 2019-01-14 | 2019-01-14 | Page cross-domain interaction method, system, device and storage device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910032143.3A CN111435380B (en) | 2019-01-14 | 2019-01-14 | Page cross-domain interaction method, system, device and storage device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111435380A CN111435380A (en) | 2020-07-21 |
| CN111435380B true CN111435380B (en) | 2024-04-16 |
Family
ID=71580461
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910032143.3A Active CN111435380B (en) | 2019-01-14 | 2019-01-14 | Page cross-domain interaction method, system, device and storage device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111435380B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112818270B (en) * | 2021-01-25 | 2023-07-25 | 上海哔哩哔哩科技有限公司 | Data cross-domain transfer method and device and computer equipment |
| CN113010610A (en) * | 2021-04-15 | 2021-06-22 | 上海绚显科技有限公司 | Data synchronization method and device |
| CN115622999A (en) * | 2022-09-28 | 2023-01-17 | 江苏谷科软件有限公司 | Safe front-end cross-domain request data interaction method |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1859170A (en) * | 2005-12-02 | 2006-11-08 | 华为技术有限公司 | Method for realizing cross-domain route separation |
| CN107580013A (en) * | 2017-07-25 | 2018-01-12 | 阿里巴巴集团控股有限公司 | The method and device of cross-domain request data |
| CN108964975A (en) * | 2018-05-30 | 2018-12-07 | 北京五八信息技术有限公司 | Cross-domain access processing method and device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170149934A1 (en) * | 2015-11-24 | 2017-05-25 | Le Holdings (Beijing) Co., Ltd. | Method, device and system for data cross-domain request |
-
2019
- 2019-01-14 CN CN201910032143.3A patent/CN111435380B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1859170A (en) * | 2005-12-02 | 2006-11-08 | 华为技术有限公司 | Method for realizing cross-domain route separation |
| CN107580013A (en) * | 2017-07-25 | 2018-01-12 | 阿里巴巴集团控股有限公司 | The method and device of cross-domain request data |
| CN108964975A (en) * | 2018-05-30 | 2018-12-07 | 北京五八信息技术有限公司 | Cross-domain access processing method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111435380A (en) | 2020-07-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109766082B (en) | Method and device for application program page jump | |
| CN107302597B (en) | Message file pushing method and device | |
| CN111062024B (en) | Application login method and device | |
| CN111435380B (en) | Page cross-domain interaction method, system, device and storage device | |
| CN110708346A (en) | Information processing system and method | |
| CN109981322B (en) | Method and device for cloud resource management based on label | |
| CN110796462A (en) | Method and device for guiding flow | |
| CN109218041B (en) | Request processing method and device for server system | |
| CN111427899A (en) | Method, device, equipment and computer readable medium for storing file | |
| CN110795328A (en) | Interface testing method and device | |
| CN111125503B (en) | Method and apparatus for generating information | |
| CN111131359B (en) | Method and apparatus for generating information | |
| CN112948138A (en) | Method and device for processing message | |
| CN111124858A (en) | Embedded point-free plug-in data processing method and system, terminal device and storage medium | |
| CN114979256B (en) | Message pushing method and device, electronic equipment and computer readable medium | |
| CN110647327A (en) | Method and device for dynamic control of user interface based on card | |
| CN113590985B (en) | Page jump configuration method and device, electronic equipment and computer readable medium | |
| CN115858905A (en) | Data processing method and device, electronic equipment and storage medium | |
| US20230418470A1 (en) | Data processing method and apparatus, and electronic device | |
| CN114610895A (en) | Work order pushing method and device, electronic equipment and storage medium | |
| CN111131354B (en) | Method and apparatus for generating information | |
| CN114417318A (en) | Third-party page jumping method and device and electronic equipment | |
| CN111767447A (en) | Method and device for determining user traffic path | |
| CN110858240A (en) | Front-end module loading method and device | |
| CN111125501A (en) | Method and apparatus for processing information |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |