CN110300133B - Cross-domain data transmission method, device, equipment and storage medium - Google Patents
Cross-domain data transmission method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN110300133B CN110300133B CN201810241240.9A CN201810241240A CN110300133B CN 110300133 B CN110300133 B CN 110300133B CN 201810241240 A CN201810241240 A CN 201810241240A CN 110300133 B CN110300133 B CN 110300133B
- Authority
- CN
- China
- Prior art keywords
- page
- data
- domain
- target
- data transmission
- 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
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
Abstract
The embodiment of the invention relates to a cross-domain data transmission method, a device, equipment and a storage medium, belonging to the technical field of communication. The method comprises the following steps: the first page obtains a second page address in a target domain, wherein the first page and the second page belong to different domains; creating a hypertext markup language tag in the first page according to the second page address to open the second page in the hypertext markup language tag; and carrying out data transmission with the target domain through the second page. Therefore, the cross-domain data transmission is realized by utilizing the page at the front end, so that the time for the cross-domain data transmission is effectively saved, the cross-domain data interaction is more convenient and efficient, and the user experience is improved.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method, an apparatus, a device, and a storage medium for transmitting cross-domain data.
Background
With the development of network technology, web applications are increasingly demanding for cross-domain data transmission. Among them, the Web application is an application program accessible through the Web, and has the greatest advantage that the application program can be used only by a browser user without installing other software.
Currently, when implementing cross-domain data transmission, generally, a web application client in a first domain first sends data to a server corresponding to the first domain (S01), so that the server corresponding to the first domain generates a corresponding token (i.e., token) according to the data (S02), and the server corresponding to the first domain sends the generated token to the web application client in the first domain (S03). Then the web application in the first domain sends the access request carrying the token to the web application client in the second domain (S04), when the web application client in the second domain receives the access request, the access request is firstly analyzed to obtain the token carried in the access request (S05), then the obtained token is sent to the server corresponding to the second domain (S06), so that the server corresponding to the second domain obtains data from the server side corresponding to the first domain according to the token (S07), and then the web application client in the second domain (S08) can directly take out the data from the server of the second domain. Optionally as shown in fig. 1.
However, the inventor finds that when the cross-domain data transmission is realized by the above method, not only web application clients in different domains are required to interact with a background server of the domain respectively, but also the transmission of key data is required to be realized by the background server, so that the transmission process of the cross-domain data not only requires higher coupling degree between the client and the server, but also takes longer time, and the user experience is poor.
Disclosure of Invention
Embodiments of the present invention aim to solve at least one of the technical problems in the related art to some extent.
To this end, an embodiment of the present invention provides a cross-domain data transmission method, including:
a first page obtains a second page address in a target domain, wherein the first page and the second page belong to different domains;
creating a hypertext markup language tag in the first page according to the second page address to open the second page in the hypertext markup language tag;
and carrying out data transmission with the target domain through the second page.
The embodiment of the invention provides a cross-domain data transmission device, which comprises:
the acquisition module is used for acquiring a second page address corresponding to a target domain by the first page, wherein the first page and the second page belong to different domains;
a creation module, configured to create a hypertext markup language tag in the first page according to the second page address, so as to open the second page in the hypertext markup language tag;
and the data transmission module is used for carrying out data transmission with the target domain through the second page.
An embodiment of the present invention provides a computer device including:
the system comprises a memory and a processor, wherein the memory stores a computer program, and the processor executes the program to realize the cross-domain data transmission method.
Embodiments of the present invention provide a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the described cross-domain data transmission method.
According to the cross-domain data transmission method, the device, the computer equipment and the storage medium, when cross-domain data transmission is carried out, the first page firstly obtains the second page address in the target domain, then the hypertext markup language tag is created in the first page according to the second page address, so that the second page is opened in the hypertext markup language tag, and then data transmission is carried out with the target domain through the second page. Therefore, the cross-domain data transmission is realized by utilizing the page at the front end, so that the time for the cross-domain data transmission is effectively saved, the cross-domain data interaction is more convenient and efficient, and the user experience is improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention as claimed.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.
FIG. 1 is a schematic diagram of data interaction in a prior art for web applications of different domains to which they belong when implementing cross-domain access;
fig. 2 is a schematic diagram of a scenario of cross-domain data transmission provided in an embodiment of the present application;
FIG. 3 is a flow chart diagram illustrating a cross-domain data transmission method according to an example embodiment;
FIG. 4 is a flow chart diagram illustrating a cross-domain data transmission method according to an example embodiment;
FIG. 5 is a schematic diagram showing a first page writing data to a second page through the second page, according to an example embodiment;
FIG. 6 is a diagram illustrating a first page writing data to a session storage area of a target domain through a second page, according to an example embodiment;
FIG. 7 is a schematic view of a scene corresponding to FIG. 6;
FIG. 8 is a flow chart illustrating a cross-domain data transmission method according to an example embodiment;
FIG. 9 is a schematic diagram showing a first page reading data from a second page through the second page, according to an example embodiment;
FIG. 10 is a diagram illustrating a first page reading data from a session storage area of a target domain through a second page according to an exemplary embodiment;
fig. 11 is a schematic diagram of a structure of a cross-domain data transmission apparatus according to an exemplary embodiment;
fig. 12 is a schematic diagram of a cross-domain data transmission apparatus according to an exemplary embodiment;
fig. 13 is a schematic diagram of a structure of a cross-domain data transmission apparatus according to an exemplary embodiment;
FIG. 14 is a schematic diagram of a computer device shown in accordance with an exemplary embodiment;
fig. 15 is a schematic structural diagram of a computer device shown according to an exemplary embodiment.
Specific embodiments of the present invention have been shown by way of the above drawings and will be described in more detail below. The drawings and the written description are not intended to limit the scope of the inventive concepts in any way, but rather to illustrate the inventive concepts to those skilled in the art by reference to the specific embodiments.
Alternative embodiments
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the invention. Rather, they are merely examples of apparatus and methods consistent with aspects of the invention as detailed in the accompanying claims.
According to the method, when the cross-domain data transmission is carried out on the existing web application, not only are web application clients in different domains required to interact with servers corresponding to the domains respectively, but also transmission of key data is realized through a background server, so that the cross-domain data transmission process is carried out by the aid of the method, the client and the server are required to have high coupling degree, more time is required, and user experience is poor.
According to the cross-domain data transmission method provided by the embodiment of the invention, when cross-domain data transmission is carried out on the first page, the second page address corresponding to the target domain is firstly obtained, wherein the first page and the second page belong to different domains, then a hypertext markup language tag is created in the first page according to the second page address so as to open the second page in the hypertext markup language tag, and then the first page can directly carry out data transmission with the target domain through the second page. Therefore, the cross-domain data transmission is realized by utilizing the page at the front end, so that the time for the cross-domain data transmission is effectively saved, the cross-domain data interaction is more convenient and efficient, and the user experience is improved.
The following first describes in detail the usage scenario of the cross-domain data transmission method provided in the embodiment of the present application with reference to fig. 2.
In practical applications, in order to increase the user quantity of each application, access tags of other applications are usually set in a client page of each application, so that a user can directly open another application in a client page of a certain application, and if the domains to which the two applications belong are different, cross-domain data transmission is generated at this time.
For example, as shown in fig. 2 (a), in the browsing page a (http:// aa.com) of the client of the a-domain Web application, an access tag of the B-domain page B (http:// bb.com) is included, if the user clicks the page B while browsing the page a, and at this time, when the B-domain logs in to the page B, if the B-domain does not have login information of the user, the login information of the user needs to be acquired from the a-domain, that is, cross-domain data transmission needs to be performed between the page a and the page B.
At this time, as shown in fig. 2 (B), the B page in the Web application client of the B domain may first create a hypertext markup language (iframe) tag in the B page according to the address of the a page in the a domain, so as to open the a page in the iframe tag, and since the iframe tag is an inline frame tag, after opening the a page in the B page in the form of the iframe tag, the B page may directly perform data transmission with the a page. For example, the B page firstly sends a request for acquiring login information to the a page, and then the a page can acquire the login information in the domain to which the a page belongs (in the drawing, session Storage is taken as an example) and return the login information to the B page.
Since the login information is usually stored in the Cookies of the domain to which the a page belongs or in a session Storage area (session Storage), the login information can be directly obtained from the Cookies corresponding to the domain to which the a page belongs or the session Storage area, without requesting the server of the a domain. Therefore, the cross-domain data transmission method provided by the embodiment of the application can realize the cross-domain data transmission directly through the page of the client without interaction between the client and the server when the cross-domain data transmission is carried out, so that the speed of the cross-domain data transmission is improved, and the time of the cross-domain data transmission is saved.
It can be appreciated that the Web application client of the a domain and the Web application client of the B domain are located in the same terminal. In one embodiment, the terminal may be a mobile terminal, which may include at least one of a cell phone, a tablet computer, a notebook computer, a personal digital assistant, a wearable device, and the like. In another embodiment, the terminal may also be a desktop computer or the like.
The following describes in detail a method, an apparatus, a device, and a storage medium for transmitting cross-domain data provided in the embodiments of the present application with reference to the accompanying drawings.
First, with reference to fig. 3, a detailed description is given of a cross-domain data transmission method provided by an embodiment of the present invention.
Fig. 3 is a flow chart illustrating a cross-domain data transmission method according to an exemplary embodiment.
As shown in fig. 3, the cross-domain data transmission method may include the steps of:
in step 201, the first page obtains a second page address in the target domain, where the first page and the second page belong to different domains.
Alternatively, the cross-domain data transmission method provided by the embodiment of the present invention may be executed by the computer device provided by the embodiment of the present invention. The cross-domain data transmission device is arranged in the computer equipment and can be configured in any Web application client, so that the Web application client can realize cross-domain data transmission at the front end.
In this embodiment, the first page and the second page refer to any page in different web applications respectively. It can be understood that the cross-domain data transmission method in this embodiment may be performed by a Web application client of a domain to which a first page belongs in a computer device, and hereinafter, the "first page" refers to the Web application client of the domain to which the first page belongs, and the "second page" refers to the Web application client of the domain to which the second page belongs.
In this embodiment, the first page refers to a page in a Web application client that initiates cross-domain data transmission; the target domain refers to another domain to be accessed by the first page, namely, other domains besides the domain to which the first page belongs; the second page may be any page under the target domain, or may also be a data transfer page specifically created for implementing cross-domain data transmission, for example, each domain may fix the address of the corresponding second page as: the present embodiment is not limited to the optional type of/xx/xxx/trans_data. Shtml, and the like.
In an optional implementation form of the application, second page addresses corresponding to other domains can be preset in each Web application client in advance, so that after the first page determines the target domain to be accessed, the second page address in the target domain can be determined by querying preset data; or, each Web application client knows the naming mode of the second page address corresponding to each other domain, so that after determining the target domain to be accessed, the first page in the Web application client can determine the second page address in the target domain according to the known naming mode of the second page address, and so on. This is not limiting here.
The hypertext markup language tag may be an Iframe tag.
Optionally, after the second page address corresponding to the target domain is obtained, the client of the domain to which the first page belongs may create an Iframe tag in the first page, for example, the src attribute value of the Iframe tag may be set to the address of the second page, so as to implement opening the second page in the form of a sub-page Iframe tag in the first page. Wherein, optionally, the second page is invisible when the second page is opened in the first page.
And 203, carrying out data transmission with the target domain through the second page.
It should be noted that, since the second page is a page in the target domain, it can directly acquire data in the target domain, or write data into the target domain, and the second page is an iFrame tag in the first page, and the iFrame tag is an inline frame tag, it can directly perform data transmission between the page where the iFrame tag is located and the page pointed to by the iFrame tag, so after the second page is opened in the first page in the form of the iFrame tag, the first page can directly perform data transmission with the second page, that is, the first page can perform data transmission with the target domain. The data transmission may include acquiring data and pushing data, among other things.
Correspondingly, the step 203 specifically includes:
and reading data from the target domain through the second page.
Or alternatively, the process may be performed,
and sending data to the second page so that the second page writes the data into a target domain to which the second page belongs.
It should be noted that, the second page may include a script with a specific function, so that the second page may perform an operation of reading data from a target domain to which the second page belongs or writing data obtained from the first page into a specific location of the target domain.
In this embodiment of the present application, if the first page is to acquire data from the target domain, after the second page is opened in the first page in the form of an Iframe tag, the first page may send a data acquisition request to the second page, and then the second page may directly read data from the domain to which the second page belongs, and then directly send the read data to the first page. Therefore, cross-domain data transmission is realized only through front-end interaction, time for cross-domain data transmission is saved, and user experience is improved.
It should be noted that, after the first page requests data to the second page, the second page may be directly obtained from the local domain, or may be requested from a server corresponding to the domain to which the second page belongs.
For example, if the data to be acquired by the first page exists in cookie, localstorage or session Storage of the domain to which the second page belongs, the second page may directly read cookie, localstorage or session Storage of the domain to which the second page belongs in the local terminal to acquire the data.
Generally, since the session Storage is a data Storage for one session, when a user does not operate the window after closing the window or within a preset duration, the data is deleted; the data in the localStorage is always valid, and the window or browser is closed and also always stored; the data in the cookie is valid only until the set cookie expiration time, even if the window or browser is closed. Therefore, the first page can access various data sequentially according to the storage characteristics of various types of data and a certain access sequence.
In an implementation manner of this embodiment, if the first page sends data to the target domain, the data to be sent may be directly sent to the second page after the second page is opened in the first page in the form of an iFrame. The second page may then store the received data in session storage, local storage, etc.
Optionally, in order to ensure the security of data transmission between the first page and the target domain, in this embodiment, data transmission between the first page and the second page may be performed in a postMessage manner.
In an alternative implementation, the first page may set a white list for the postMessage, so that before data transmission is performed with the second page, whether the target domain is in the white list is first determined, if yes, the target domain is determined to be legal, and then data transmission is performed with the target domain through the second page.
In an alternative implementation, it may be determined whether the target domain to which the second page belongs is in the white list before the iFrame tag is created in the first page. In another alternative implementation, it may also be determined whether the target domain to which the second page belongs is in the white list after the iFrame tag is created in the first page. In another alternative implementation, different whitelists may also be set according to the type or amount of data transmitted across the domains. For example, the domain a is a whitelist X set for postMessage, which is used for verifying the validity of the data transferred across domains when the data transferred across domains is login information, and the whitelist Y is set for verifying the validity of the data transferred across domains when the data transferred across domains is "payment" information, and the domain names included in the whitelist X and the whitelist Y are not identical. Thus, when the domain a is transmitting cross-domain, if the currently transmitted data is determined to be login information, whether the current target domain is in the white list X can be judged, and if so, the login information can be transmitted to the target domain or the login information can be acquired from the target domain.
According to the cross-domain data transmission method provided by the embodiment of the invention, the first page firstly acquires the second page address in the target domain, then the hypertext markup language tag is created in the first page according to the second page address, so that the second page is opened in the hypertext markup language tag, and then data transmission is carried out between the second page and the target domain. Therefore, the cross-domain data transmission is realized by utilizing the page at the front end, so that the time for the cross-domain data transmission is effectively saved, the cross-domain data interaction is more convenient and efficient, and the user experience is improved.
As can be seen from the above analysis, in the embodiment of the present invention, the hypertext markup language tag is created in the first page, so that the second page belonging to the target domain is opened in the hypertext markup language tag, and data is transmitted between the second page and the target domain. When the first page performs data transmission with the target domain through the second page, the data may be pushed to the target domain through the second page, or the data may be obtained from the target domain through the second page. The process of pushing data to the target domain by the first page through the second page will be described in detail with reference to fig. 4.
Fig. 4 is a flow chart illustrating a cross-domain data transmission method according to an exemplary embodiment.
As shown in fig. 4, the cross-domain data transmission method may include the steps of:
in step 301, the first page obtains a second page address in the target domain, where the first page and the second page belong to different domains.
The first page can directly send the data push request to the second page after the second page is opened; or, when the Iframe tag is created, the data to be pushed can be directly carried in the parameter of the Iframe tag, so that after the second page is opened, the data pushing request can be obtained according to the parameter of the Iframe tag.
In order to facilitate the validity verification of the first page by the subsequent target domain, when the first page sends a data push request to the target domain, the first page may carry its own identification information in the data push request, so that when the second page receives the data push request, the second page verifies the identity validity of the first page.
The identification information may be a domain name of the domain to which the first page belongs, or an ID, etc., which is not limited in this embodiment.
And step 303, receiving a receiving response message returned by the second page.
The receiving response message may be a postMessage-ready message.
In this embodiment, after the first page sends the data push request to the second page, the first page may monitor, according to a preset monitor, a message received by the second page, so as to receive a receiving response message returned by the second page. In this embodiment, the preset listener may be located on the second page.
In addition, after the second page obtains the data push request sent by the first page, the data push request can be analyzed first to obtain the identification information of the first page carried in the data push request, and then the identification information is matched with a preset white list. If the matching is successful, determining that the first page is legal, and if the matching is failed, determining that the first page is illegal. When it is determined that the first page is legal, the second page may send a reception response message, namely postMessage-ready, to the first page.
And step 304, transmitting data to the second page.
Optionally, after the first page receives the receiving response message returned by the second page, the first page may send corresponding data to the second page, so that the second page writes the data into the target domain.
The following further describes, by taking the first page pushing data to the second page, taking writing the acquired data into the sessionStorage by the second page as an example, the process of pushing data from the first page to the target domain by using fig. 5:
assuming that the first page is a master station and the second page is a third party located in a Web client of the master station, the process of pushing data to the third party by the master station may include the following steps:
step 10: the master station acquires a second page address corresponding to a domain to which a third party belongs: /mb/inc/trans_data. Shtml;
step 11: the master station establishes an Iframe tag according to the/mb/inc/trans_data.shtml so as to open a second page through the Iframe tag and send a data push request (a) to the second page;
step 12: a third party analyzes the received new message and checks the validity of the master station;
step 13: if the master station is determined to be legal, a receiving response message (namely postMessage-ready) is sent to the master station;
Step 14: and when the master station monitors postMessage-ready returned by the third party, pushing corresponding data to the third party by using the postMessage.
Optionally, in an exemplary embodiment of the present invention, after the first page writes data into the session storage area of the target domain through the second page, a third page of the target domain may be further called up through the first page, so that the third page performs page rendering according to the data written in the session storage area, so that a user may view a data writing result, or perform operations such as payment on the third page.
The third page may be an interface for completing writing of data, or a payment operation interface, etc., which is not limited herein.
In order to more clearly describe the embodiments of the present invention, the following possible implementation scenarios are taken as examples, and the process of pushing data by the first page object provided in the embodiments of the present application is further described below with reference to fig. 6 and fig. 7.
The realization scene is as follows: the B-domain Web application has an access tag in a page of the A-domain Web application, a user opens the B-domain Web application in the A-domain Web client through the access tag, and purchases goods in the B-domain Web application, but the B-domain Web application cannot pay, and needs to jump back to a payment page of the A-domain Web application to pay the goods. When the B-domain Web application jumps back to the payment interface of the A-domain Web application to pay for goods, the corresponding data transmission is that the B-domain Web application loads a second page of the A-domain Web application by using the access tag, and then the transaction data is pushed to the A-domain Web application, so that the A-domain Web application renders the payment page according to the transaction data sent by the B-domain Web application, and the payment operation is performed. Alternatively, the data transmission process between the a-domain and the B-domain is shown in fig. 6 and 7, wherein fig. 6 is a signaling diagram of the data transmission process, and fig. 7 is a schematic diagram of a scenario.
S1, a user jumps from an A domain Web application to a B domain Web application;
s2, detecting a login state of a local (session) non-user by the B domain web;
s3, loading a second page of the A domain by using the iframe tag in the current page by the B domain web;
s4, the second page of the A domain sends login state data to the web of the B domain through postMessage;
s5, the B domain web performs login page rendering by using login state data;
s6, the user purchases goods in the B-domain web and initiates a payment process;
s7, loading a second page of the A domain by the B domain web by using an iframe tag;
s8, pushing the transaction data to the Web in the A domain;
s9, after the B domain web determines that the transaction data pushing is finished, jumping to a payment page in the A domain;
and S10, rendering the payment page by the A domain according to the acquired data so as to enable the user to carry out payment operation.
After payment is completed, the user can continue to jump back to the B-domain web page or leave the A-domain web page as required.
Optionally, if the step of jumping back to the B-domain web page after the payment is completed is to be implemented, the B-domain may push the page address to be jumped back to the a-domain when the transaction data is pushed to the a-domain, so that the a-domain payment page may simultaneously acquire the page address to be jumped back when the transaction data is acquired, and further directly jump back to the B-domain according to the address after the payment is determined to be completed.
According to the cross-domain data transmission method provided by the embodiment of the invention, the first page loads the second page in the target domain by using the iframe tag, then the data to be pushed is sent to the second page by using the PostMessage, and then the data to be pushed is written into the target domain by using the second page. Therefore, cross-domain data transmission by utilizing the front-end page is realized, so that the time for data transmission among pages in different domains is effectively saved, the data interaction is more convenient and efficient, the user experience is improved, the cross-domain data transmission is performed through PostMessage, the data safety is ensured, and the condition is provided for protecting the data safety for the user.
Through the analysis, the first page can directly push data to the target domain through front-end page interaction. In another aspect of the present invention, the first page may also read data from the target domain through the second page to perform a corresponding operation according to the read data. The process of reading data from the target domain by the first page through the second page will be described in detail with reference to fig. 8.
Fig. 8 is a flow chart illustrating a cross-domain data transmission method according to an exemplary embodiment.
As shown in fig. 8, the cross-domain data transmission method may include the steps of:
In step 601, the first page obtains a second page address in the target domain, where the first page and the second page belong to different domains.
The target data identifier to be acquired can be determined according to actual needs, which is not limited in this embodiment.
For example, if the first page currently needs login information, the login information may be determined as target data, and the administtrator may be used as an identifier of the target data.
The data reading request may include: target data identification to be acquired, identification information of a first page, and the like.
It can be understood that, in order to facilitate the subsequent verification of the validity of the first page by the second page, when the first page sends a data reading request to the second page, the first page may carry its own identification information in the data reading request, so that when the second page receives the data reading request, the second page verifies the validity of the first page.
The identification information may be a domain name of the domain to which the first page belongs, or an ID, etc., which is not limited in this embodiment.
Optionally, after the first page sends the data reading request to the second page, the message sent by the second page may be monitored according to a preset monitor, so as to receive the target data returned by the second page.
In addition, after the second page obtains the data reading request sent by the first page, the data reading request can be analyzed first to obtain the identification information of the first page carried in the data reading request, and then the identification information is matched with a preset white list. If the matching is successful, determining that the first page is legal, and if the matching is failed, determining that the first page is illegal. When the first page is determined to be legal, the second page can read corresponding target data from the target domain according to the target data identifier to be acquired, which is carried in the data reading request, and send the target data to the first page, so that the first page executes corresponding operation according to the target data.
In this embodiment, legal domain names are stored in a preset white list, and the preset white list may be set by default or user-defined, which is not limited in this embodiment.
The procedure of reading data from the session storage area of the target domain by the first page through the second page is exemplarily described below with reference to fig. 9:
assuming that the first page is a page in the a-domain Web application and the second page is a page in the B-domain Web application, when the a-domain Web application reads data from the session of the B-domain Web application, the method may include the following steps:
step 20: the A domain Web application client acquires a second page address corresponding to the B domain Web application: /mb/inc/trans_data. Shtml;
step 21: and the A domain Web application client establishes an Iframe tag according to the/mb/inc/trans_data. Shtml so as to send a data reading request a to the B domain through a second page.
The data reading request may carry the target data identifier b to be obtained.
Step 22: and the B domain Web application client analyzes the received data reading request a to determine the legitimacy of the A domain Web application client.
The B domain Web application client can monitor the second page through a preset monitor to acquire the data reading request message.
Step 23: if the domain A is legal, reading corresponding target data from session of the domain according to the target data identifier b to be obtained in the data reading request a;
Step 24: and the second page in the B-domain Web application client sends the target data to the A-domain Web application client page by using the PostMessage.
Optionally, in practical application, since the data information stored in the session storage area of the domain to which the page belongs generally has a valid time, when the second page acquires the target data from the session storage area of the target domain according to the target data identifier to be acquired, there is a case that the acquisition fails. At this time, in order to enable the second page to acquire the data in time, the present embodiment may further determine a fourth page address corresponding to the target data in the target domain when the acquisition of the target data fails, and further jump back to the fourth page according to the fourth page address, so as to acquire the corresponding target data by performing further operations on the fourth page.
Next, in connection with fig. 10, a case where when the first page reads data into the session storage area of the target domain through the second page, there is no data to be read in the target domain will be described in detail.
Assuming that the first page is a page in the A-domain Web application client, the second page is a page in the B-domain Web application client, and the process of directly accessing the B-domain Web application from the A-domain Web client by the user is selected as follows:
S1, a user jumps to a B domain Web application from a page in an A domain Web application client;
s2, detecting a login state of a local non-user by the B domain Web application client;
s3, the B domain Web application client loads a second page of the A domain in the current page by using the iframe tag;
s4, the B domain Web application client determines that login state data returned by the second page is not acquired;
when the B-domain Web application client obtains login state data from the a-domain Web application client through the second page, the B-domain Web application client may not obtain the login state data through the second page because the login state data stored in the a-domain exceeds the time efficiency or the login state data is not available.
S5, the B domain Web application client determines a login page address corresponding to login state data in the A domain;
s6, the Web application client in the B domain jumps back to the login page in the A domain;
the B domain Web application client jumps back to the login page in the A domain, the corresponding data transmission can be selected as that the B domain Web application client loads a second page of the A domain by using the access tag, and then the login page address data is pushed to the A domain, so that the A domain loads the corresponding login page according to the login page address sent by the B domain Web application.
S7, the B domain Web application client performs login authentication on a login page;
s8, jumping back to the B domain Web application client;
s9, the B domain Web application client loads a second page of the A domain in the current page by using the iframe tag;
s10, the second page sends login state data to the B domain Web application client through postMessage;
and S11, the B domain Web application client uses the login state data to render the login page.
According to the cross-domain data transmission method provided by the embodiment of the invention, firstly, the first page loads the second page in the target domain by using the iframe tag, then the second page reads corresponding target data from the target domain, and the read target data is sent to the first page through the PostMessage. Therefore, the cross-domain data transmission is realized by utilizing the page at the front end, so that the time for the cross-domain data transmission is effectively saved, the cross-domain data interaction is more convenient and efficient, and the user experience is improved. And the cross-domain data transmission is carried out through the PostMessage, so that the data security is ensured, and conditions are provided for protecting the data security for users.
In an exemplary embodiment, a cross-domain data transmission apparatus is also provided.
Fig. 11 is a schematic structural diagram of a cross-domain data transmission apparatus according to an exemplary embodiment.
Referring to fig. 11, a cross-domain data transmission apparatus of the present invention includes: the acquisition module 110, the creation module 120, and the data transmission module 130.
The acquiring module 110 is configured to enable a first page to acquire a second page address in a target domain, where the first page and the second page belong to different domains;
the creation module 120 is configured to create a hypertext markup language tag in the first page according to the second page address, so as to open the second page in the hypertext markup language tag;
the data transmission module 130 is configured to perform data transmission with the target domain through the second page.
In an alternative implementation form, the data transmission module 130 is specifically configured to:
reading data from the target domain through the second page;
or alternatively, the process may be performed,
and sending data to the second page so that the second page writes the data into a target domain to which the second page belongs.
It should be noted that the foregoing explanation of the embodiment of the cross-domain data transmission method is also applicable to the cross-domain data transmission device of this embodiment, and the implementation principle is similar, which is not repeated herein.
The cross-domain data transmission device can be configured in any Web application client so that the Web application can interact with pages of other domains through a foreground to perform cross-domain data transmission.
According to the cross-domain data transmission device provided by the embodiment of the invention, the first page firstly acquires the second page address in the target domain, then the hypertext markup language tag is created in the first page according to the second page address, so that the second page is opened in the hypertext markup language tag, and then data transmission is carried out between the second page and the target domain. Therefore, the cross-domain data transmission is realized by utilizing the page at the front end, so that the time for the cross-domain data transmission is effectively saved, the cross-domain data interaction is more convenient and efficient, and the user experience is improved.
Fig. 12 is a schematic structural diagram of a cross-domain data transmission apparatus according to an exemplary embodiment.
Referring to fig. 12, the cross-domain data transmission apparatus may include:
the acquiring module 110 is configured to enable a first page to acquire a second page address in a target domain, where the first page and the second page belong to different domains;
the creation module 120 is configured to create a hypertext markup language tag in the first page according to the second page address, so as to open the second page in the hypertext markup language tag;
in an alternative implementation form, the cross-domain data transmission device of the embodiment of the present invention further includes: a receiving module 140.
The receiving module 140 is configured to receive a receiving response message returned by the second page.
In an alternative implementation form, the cross-domain data transmission device of the embodiment of the present invention further includes: and a rendering module 150.
The rendering module 150 is configured to call up a third page in the target domain, so that the third page performs page rendering according to the data written in the target domain.
It should be noted that the foregoing explanation of the embodiment of the cross-domain data transmission method is also applicable to the cross-domain data transmission device of this embodiment, and the implementation principle is similar, which is not repeated herein.
According to the cross-domain data transmission device provided by the embodiment of the invention, the first page loads the second page in the target domain by using the iframe tag, then the data to be pushed is sent to the second page by using the PostMessage, and then the data to be pushed is written into the target domain by using the second page. Therefore, cross-domain data transmission by utilizing the front-end page is realized, so that the time for data transmission among pages in different domains is effectively saved, the data interaction is more convenient and efficient, the user experience is improved, the cross-domain data transmission is performed through PostMessage, the data safety is ensured, and the condition is provided for protecting the data safety for the user.
Fig. 13 is a schematic structural diagram of a cross-domain data transmission apparatus according to an exemplary embodiment.
Referring to fig. 13, the cross-domain data transmission apparatus may include:
the acquiring module 110 is configured to enable a first page to acquire a second page address in a target domain, where the first page and the second page belong to different domains;
in an alternative implementation form, the cross-domain data transmission device of the embodiment of the present invention further includes: the first determination module 160.
The first determining module 160 is configured to determine a target data identifier to be acquired;
the creation module 120 is configured to create a hypertext markup language tag in the first page according to the second page address, so as to open the second page in the hypertext markup language tag;
the data transmission module 130 is configured to send a data reading request to the second page;
the data reading request may include: target data identification to be acquired, identification information of a first page, and the like.
In an alternative implementation form, the data transmission module 130 is specifically configured to:
and reading target data from the target domain through the second page according to the target data identification to be acquired.
In an alternative implementation form, the cross-domain data transmission device of the embodiment of the present invention further includes:
a second determining module, configured to determine an address of a fourth page in the target domain corresponding to the target data if the target data is not included in the target domain;
and the jump module is used for jumping back to the fourth page according to the address of the fourth page.
In an alternative implementation form, the cross-domain data transmission device of the embodiment of the present invention further includes: and a third determination module. And the third determining module is used for determining that the target domain is legal.
It should be noted that the foregoing explanation of the embodiment of the cross-domain data transmission method is also applicable to the cross-domain data transmission device of this embodiment, and the implementation principle is similar, which is not repeated herein.
According to the cross-domain data transmission method provided by the embodiment of the invention, firstly, the first page loads the second page in the target domain by using the iframe tag, then the second page reads corresponding target data from the target domain, and the read target data is sent to the first page through the PostMessage. Therefore, the cross-domain data transmission is realized by utilizing the page at the front end, so that the time for the cross-domain data transmission is effectively saved, the cross-domain data interaction is more convenient and efficient, and the user experience is improved. And the cross-domain data transmission is carried out through the PostMessage, so that the data security is ensured, and conditions are provided for protecting the data security for users.
In an exemplary embodiment, a computer device is also provided.
Fig. 14 is a schematic structural diagram of a computer device according to an exemplary embodiment. The computer device shown in fig. 14 is only an example, and should not be construed as limiting the functionality and scope of use of the embodiments of the invention.
Referring to fig. 14, the computer apparatus 200 includes: a memory 210 and a processor 220, the memory 210 storing a computer program which, when executed by the processor 220, causes the processor 220 to perform the steps of: a first page obtains a second surface address in a target domain, wherein the first page and the second page belong to different domains; creating a hypertext markup language tag in the first page according to the second page address to open the second page in the hypertext markup language tag; and carrying out data transmission with the target domain through the second page. .
In one embodiment, the data transmission with the target domain through the second page includes: reading data from the target domain through the second page; or sending data to the second page so that the second page writes the data into a target domain to which the second page belongs.
In one embodiment, before the sending data to the second page, the method further includes: and receiving a receiving response message returned by the second page.
In one embodiment, after the sending data to the second page, the method further includes: and calling up a third page in the target domain, so that the third page performs page rendering according to the data written in the target domain.
In one embodiment, before the creating the hypertext markup language tag, the method further comprises: determining a target data identifier to be acquired; the reading data from the target domain through the second page includes: and reading target data from the target domain through the second page according to the target data identification to be acquired.
In one embodiment, after the reading the target data from the target domain through the second page, the method further includes: if the target domain does not contain the target data, determining an address of a fourth page in the target domain, which corresponds to the target data; and jumping back to the fourth page according to the address of the fourth page.
In one embodiment, before the data transmission with the target domain through the second page, the method further includes: and determining that the target domain is legal.
In an alternative implementation, as shown in fig. 15, the computer device 200 may further include: the memory 210 and the processor 220, the bus 230 connecting different components (including the memory 210 and the processor 220), the memory 210 stores a computer program, and the processor 220 implements the cross-domain data transmission method according to the embodiment of the present invention when executing the program.
Program/utility 280 having a set (at least one) of program modules 270 may be stored in, for example, memory 210, such program modules 270 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment. Program modules 270 generally perform the functions and/or methods of the embodiments described herein.
The computer device 200 may also communicate with one or more external devices 290 (e.g., keyboard, pointing device, display 291, etc.), one or more devices that enable a user to interact with the computer device 200, and/or any device (e.g., network card, modem, etc.) that enables the computer device 200 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 292. Moreover, computer device 200 may also communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN) and/or a public network, such as the Internet, through network adapter 293. As shown, network adapter 293 communicates with other modules of computer device 200 over bus 230. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with computer device 200, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.
The processor 220 executes various functional applications and data processing by running programs stored in the memory 210.
It should be noted that the foregoing explanation of the embodiment of the cross-domain data transmission method is also applicable to the computer device of this embodiment, and the implementation principle is similar, which is not repeated herein.
According to the computer equipment provided by the embodiment of the invention, the first page firstly acquires the second page address in the target domain, then the hypertext markup language tag is created in the first page according to the second page address, so that the second page is opened in the hypertext markup language tag, and then data transmission is carried out between the second page and the target domain. Therefore, the cross-domain data transmission is realized by utilizing the page at the front end, so that the time for the cross-domain data transmission is effectively saved, the cross-domain data interaction is more convenient and efficient, and the user experience is improved.
In an exemplary embodiment, the invention also proposes a computer-readable storage medium.
The above computer readable storage medium has stored thereon a computer program which, when executed by a processor, implements the cross-domain data transmission method described in the embodiment.
In the description of the present invention, it should be understood that the terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying a relative importance or number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include one or more such feature. In the description of the present invention, the meaning of "a plurality" is two or more, unless explicitly defined otherwise as optional.
In the description of the present specification, descriptions of the terms "one embodiment," "some embodiments," "examples," "alternative examples," or "some examples," etc., mean that an alternative feature or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present invention. In this specification, schematic representations of the above terms are not necessarily directed to the same embodiment or example. Furthermore, the described optional features or characteristics may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, the different embodiments or examples described in this specification and the features of the different embodiments or examples may be combined and combined by those skilled in the art without contradiction.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and further implementations are included within the scope of the preferred embodiment of the present invention in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present invention.
Logic and/or steps represented in the flowcharts or otherwise described herein, e.g., a ordered listing of executable instructions for implementing logical functions, can alternatively be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. More alternative examples (a non-exhaustive list) of the computer readable medium include the following: an electrical connection (electronic device) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). In addition, the computer readable medium may even be paper or other suitable medium on which the program is printed, as the program may be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory.
It is to be understood that portions of the present invention may be implemented in hardware, software, firmware, or a combination thereof. In the above-described embodiments, the various steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, may be implemented using any one or combination of the following techniques, as is well known in the art: discrete logic circuits having logic gates for implementing logic functions on data signals, application specific integrated circuits having suitable combinational logic gates, programmable Gate Arrays (PGAs), field Programmable Gate Arrays (FPGAs), and the like.
Those of ordinary skill in the art will appreciate that all or a portion of the steps carried out in the method of the above-described embodiments may be implemented by a program to instruct related hardware, where the program may be stored in a computer readable storage medium, and where the program, when executed, includes one or a combination of the steps of the method embodiments.
In addition, each functional unit in the embodiments of the present invention may be integrated in one processing module, or each unit may exist alone physically, or two or more units may be integrated in one module. The integrated modules may be implemented in hardware or in software functional modules. The integrated modules may also be stored in a computer readable storage medium if implemented in the form of software functional modules and sold or used as a stand-alone product.
The above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, or the like. While embodiments of the present invention have been shown and described above, it will be understood that the above embodiments are illustrative and not to be construed as limiting the invention, and that variations, modifications, alternatives and variations may be made to the above embodiments by one of ordinary skill in the art within the scope of the invention.
Claims (7)
1. A method for cross-domain data transmission, comprising:
a first page obtains a second page address in a target domain, wherein the first page and the second page belong to different domains;
determining a target data identifier to be acquired;
creating a hypertext markup language tag in the first page according to the second page address to open the second page in the hypertext markup language tag;
and carrying out data transmission with the target domain through the second page, wherein the data transmission comprises the following steps:
according to the target data identifier to be acquired, reading target data from the target domain through the second page, including: sending a data reading request to the second page, wherein the data reading request carries the target data identifier to be acquired and the identification information of the first page, so that the second page verifies the validity of the first page according to the identification information of the first page carried by the data reading request, and when the first page is determined to be legal, the second page reads corresponding target data from the target domain according to the target data identifier to be acquired carried by the data reading request and sends the target data to the first page; receiving the target data returned by the second page;
Or alternatively, the process may be performed,
sending a data push request to the second page to send the data push request to the target domain through the second page, wherein the data push request carries the identification information of the first page, so that the second page verifies the validity of the first page according to the identification information of the first page carried by the data push request, and when the first page is determined to be legal, the second page sends a receiving response message to the first page, and the receiving response message is generated by the target domain through responding to the data push request; receiving a receiving response message returned by the second page; and sending data to the second page so that the second page writes the data into a target domain to which the second page belongs.
2. The method of claim 1, wherein after the sending data to the second page, further comprising:
and calling up a third page in the target domain, so that the third page performs page rendering according to the data written in the target domain.
3. The method of claim 1, wherein after the reading of the target data from the target domain through the second page, further comprising:
If the target domain does not contain the target data, determining an address of a fourth page in the target domain, which corresponds to the target data;
and jumping back to the fourth page according to the address of the fourth page.
4. A method according to any one of claims 1-3, wherein prior to said data transfer with said destination domain via said second page, further comprising:
and determining that the target domain is legal.
5. A cross-domain data transmission apparatus, comprising:
the acquisition module is used for acquiring a second page address in a target domain by a first page, wherein the first page and the second page belong to different domains;
the first determining module is used for determining a target data identifier to be acquired;
a creation module, configured to create a hypertext markup language tag in the first page according to the second page address, so as to open the second page in the hypertext markup language tag;
the data transmission module is configured to perform data transmission with the target domain through the second page, and includes:
according to the target data identifier to be acquired, reading target data from the target domain through the second page, including: sending a data reading request to the second page, wherein the data reading request carries the target data identifier to be acquired and the identification information of the first page, so that the second page verifies the validity of the first page according to the identification information of the first page carried by the data reading request, and when the first page is determined to be legal, the second page reads corresponding target data from the target domain according to the target data identifier to be acquired carried by the data reading request and sends the target data to the first page; receiving the target data returned by the second page;
Or alternatively, the process may be performed,
sending a data push request to the second page to send the data push request to the target domain through the second page, wherein the data push request carries the identification information of the first page, so that the second page verifies the validity of the first page according to the identification information of the first page carried by the data push request, and when the first page is determined to be legal, the second page sends a receiving response message to the first page, and the receiving response message is generated by the target domain through responding to the data push request; receiving a receiving response message returned by the second page; and sending data to the second page so that the second page writes the data into a target domain to which the second page belongs.
6. A computer device, comprising: a memory and a processor, the memory storing a computer program, wherein the processor implements the cross-domain data transmission method according to any one of claims 1-4 when executing the program.
7. A computer readable storage medium having stored thereon a computer program, which when executed by a processor, implements a cross-domain data transmission method according to any of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810241240.9A CN110300133B (en) | 2018-03-22 | 2018-03-22 | Cross-domain data transmission method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810241240.9A CN110300133B (en) | 2018-03-22 | 2018-03-22 | Cross-domain data transmission method, device, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110300133A CN110300133A (en) | 2019-10-01 |
| CN110300133B true CN110300133B (en) | 2023-04-28 |
Family
ID=68025756
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810241240.9A Active CN110300133B (en) | 2018-03-22 | 2018-03-22 | Cross-domain data transmission method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110300133B (en) |
Families Citing this family (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111209557A (en) * | 2019-12-24 | 2020-05-29 | 中移（杭州）信息技术有限公司 | Cross-domain single sign-on method and device, electronic equipment and storage medium |
| CN111327598B (en) * | 2020-01-21 | 2022-04-19 | 深圳前海环融联易信息科技服务有限公司 | Project login-free method and device, computer equipment and storage medium |
| CN111339460B (en) * | 2020-02-10 | 2024-03-01 | 广州虎牙科技有限公司 | Data updating method, device, computer equipment and storage medium |
| CN111475228A (en) * | 2020-04-03 | 2020-07-31 | 弦子科技(北京)有限公司 | Data interaction method, device and equipment based on framework and storage medium |
| CN111859233A (en) * | 2020-06-01 | 2020-10-30 | 中煤电气有限公司 | Data interaction method, system, computer device and readable storage medium |
| CN112818270B (en) * | 2021-01-25 | 2023-07-25 | 上海哔哩哔哩科技有限公司 | Data cross-domain transfer method and device and computer equipment |
| CN113285936B (en) * | 2021-05-14 | 2023-10-31 | 深圳市金蝶天燕云计算股份有限公司 | Cross-domain data acquisition method and related device |
| CN113296762B (en) * | 2021-06-21 | 2023-07-21 | 北京有竹居网络技术有限公司 | Page embedding method and device, storage medium and electronic equipment |
| CN114760139A (en) * | 2022-04-21 | 2022-07-15 | 北京金堤科技有限公司 | Login state synchronization method and device, electronic equipment and computer storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101771676A (en) * | 2008-12-31 | 2010-07-07 | 华为技术有限公司 | Setting and authentication method for cross-domain authorization and relevant device and system |
| CN105187426A (en) * | 2015-09-06 | 2015-12-23 | 北京京东尚科信息技术有限公司 | Method and system for realizing cross-domain access on the basis of authentication information |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8250082B2 (en) * | 2006-06-23 | 2012-08-21 | Microsoft Corporation | Cross domain communication |
| GB2494027B (en) * | 2011-08-25 | 2014-05-21 | Ibm | A computer-implemented method enabling a web application to call at least one native function of a mobile device |
| CN103207863B (en) * | 2012-01-13 | 2016-12-07 | 腾讯科技（深圳）有限公司 | Page cross-domain alternation method and terminal |
| CN103309877B (en) * | 2012-03-12 | 2017-04-05 | 腾讯科技（深圳）有限公司 | The method of cross-domain communication and full duplex communication, device |
| CN103546570A (en) * | 2013-10-29 | 2014-01-29 | 小米科技有限责任公司 | Method, device and terminal for achieving network client-side cross-domain data request |
| CN104301379A (en) * | 2014-08-28 | 2015-01-21 | 北京奇虎科技有限公司 | Web page cross-domain communication method and device |
| CN104317819A (en) * | 2014-09-28 | 2015-01-28 | 北京京东尚科信息技术有限公司 | Method and system for webpage cross-domain communication based on browsers |
| CN104504096B (en) * | 2014-12-26 | 2019-02-01 | 北京奇虎科技有限公司 | A kind of information transferring method and web page browsing device of inter-network page |
| US9762595B2 (en) * | 2015-08-11 | 2017-09-12 | Raytheon Company | Secure cross domain solution systems and methods |
-
2018
- 2018-03-22 CN CN201810241240.9A patent/CN110300133B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101771676A (en) * | 2008-12-31 | 2010-07-07 | 华为技术有限公司 | Setting and authentication method for cross-domain authorization and relevant device and system |
| CN105187426A (en) * | 2015-09-06 | 2015-12-23 | 北京京东尚科信息技术有限公司 | Method and system for realizing cross-domain access on the basis of authentication information |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110300133A (en) | 2019-10-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110300133B (en) | Cross-domain data transmission method, device, equipment and storage medium | |
| US10681028B2 (en) | Controlling access to resources on a network | |
| US9769266B2 (en) | Controlling access to resources on a network | |
| US8856957B1 (en) | Federated identity broker | |
| CN110839087B (en) | Interface calling method and device, electronic equipment and computer readable storage medium | |
| JP5707542B2 (en) | Encoding labels in values to understand the flow of information | |
| CN107015996A (en) | A kind of resource access method, apparatus and system | |
| CN111160845A (en) | Service processing method and device | |
| US9210159B2 (en) | Information processing system, information processing device, and authentication method | |
| CN108881228A (en) | Cloud registration activation method, device, equipment and storage medium | |
| US10659516B2 (en) | Data caching and resource request response | |
| US11770385B2 (en) | Systems and methods for malicious client detection through property analysis | |
| CN104158818A (en) | Single sign-on method and system | |
| US20140150055A1 (en) | Data reference system and application authentication method | |
| CN109819033A (en) | A kind of resource file loading method and system | |
| CN106254528A (en) | A kind of resource downloading method and buffer memory device | |
| CN111241523B (en) | Authentication processing method, device, equipment and storage medium | |
| CN111538922B (en) | Link jump method, application client, device and storage medium | |
| CN113239308A (en) | Page access method, device, equipment and storage medium | |
| CN104009999A (en) | Method and device for preventing ARP cheating and network access server | |
| CN111459819B (en) | Software testing method and device, electronic equipment and computer readable medium | |
| US10742802B2 (en) | Methods and devices for verifying a communication number | |
| US20140325605A1 (en) | System for storage security of cloud server in cloud computing environment and method thereof | |
| CN114389851B (en) | Switch maintenance service identity verification method, system, terminal and storage medium | |
| CN112751844B (en) | Portal authentication method and device and electronic equipment |
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 |