CN104301379A - A webpage cross-domain communication method and device - Google Patents

Abstract

The invention discloses a web page cross-domain communication method and device. The method includes the steps that a first page with a first root domain name loads a second webpage with a second root domain name in the first page in an embedding mode; the second page adds target data from the second root domain name into a preset third page and skips to the third page, and the root domain name of the third page is the first root domain name; the third page extracts the contained target data from the second root domain name and stores the target data in storage space which the pages with the first root domain name can have access to; the first page reads the target data from the second root domain name from the storage space. The communication between the cross-domain web pages in a browser is achieved, cross-domain file transmission, data sharing and data synchronization can be achieved, meanwhile, the development cost is lowered, and the problem that different root domain names are mutually embedded is solved.

Description

A webpage cross-domain communication method and device

technical field

The present invention relates to the technical field of webpage processing, in particular to a webpage cross-domain communication method and a webpage cross-domain communication device.

Background technique

In order to avoid security problems caused by mutual interference between web pages, in JavaScript, there is a very important security restriction called Same-Origin Policy (Same-Origin Policy), which prevents documents or scripts loaded from one source Gets or sets a property of a document loaded by another source.

For example, http://www.360.cn/index.html and http://www.qihoo.com/index.html are respectively opened in the two tab pages of the browser, where JavaScript1 and JavaScript3 belong to sina script, and JavaScript2 is a script belonging to 163. When tab1 of the browser wants to run a script, it will perform a same-origin check, and only scripts with the same origin as www.360.com can be executed. Therefore, tab1 can only execute JavaScript1 and JavaScript3 scripts, but JavaScript2 cannot, thereby preventing illegal tampering of this webpage by other webpages.

At present, browsers that support JavaScript generally use the same-origin policy, which prevents data communication between web pages of different origins and loses the convenience of cross-domain data transfer.

Contents of the invention

In view of the above problems, the present invention is proposed to provide a web page cross-domain communication method and a corresponding web page cross-domain communication device that overcome the above problems.

According to one aspect of the present invention, a webpage cross-domain communication method is provided, including:

The first page with the first root domain name loads the second page with the second root domain name in an embedded manner in the first page;

The second page adds target data originating from the second root domain name to a preset third page, and jumps to the third page, where the root domain name of the third page is the first root domain name;

The third page extracts the target data contained in the second root domain name, and saves it in a storage space accessible to pages with the first root domain name;

The first page reads the target data originating from the second root domain name from the storage space.

Optionally, the first page with the first root domain name loading the second page with the second root domain name in an embedded manner in the first page includes:

The first page sends a data processing request to the second server corresponding to the second root domain name;

After sending the data processing request, the embedded page preset in the first page loads the page address of the second page to obtain the second page.

Optionally, the first page includes a form element, the target source address of the form element is the page address of the second page, and the embedded page is preset in the form element.

Optionally, the first page sending the data processing request to the second server corresponding to the second root domain name includes:

The form element of the first page sends a post request to the second server to upload data to the second server, and the post request carries the data requested to be processed;

Or, the form element of the first page sends a get request to the second server to obtain data from the second server, and the get request carries the data requested to be processed.

Optionally, the embedded page preset in the first page loads the page address of the second page, and the obtained second page includes:

The embedded page in the form element loads the target source address of the form element to obtain the second page.

Optionally, the target data includes all data processing results, partial data processing results, or attribute information of the data processing results obtained from the data processing request sent by the server corresponding to the second root domain name for the first page.

Optionally, adding target data originating from the second root domain name to a preset third page on the second page, and jumping to the third page includes:

The second page corresponds to the storage address of the first server or the second server corresponding to the first root domain name and the page address of the third page organized by the first root domain name according to the target data;

The second page jumps to the third page according to the page address of the organization.

Optionally, the target data derived from the second root domain name included in the extraction of the third page includes:

The third page extracts the storage address corresponding to the target data originating from the second root domain name from the page address of the third page;

Extract target data from the first server or the second server according to the storage address.

Optionally, the saving to the accessible storage space of the page with the first root domain name includes:

saving the target data originating from the second root domain name in a storage space designated locally for the first root domain name and identified by the first root domain name;

Or, the target data originating from the second root domain name is saved in a local storage space as a file, and the file name of the target data is recorded in the file directory.

Optionally, the method also includes:

After the target data is saved to the storage space accessible by the page with the first root domain name, or after the loading of the third page is completed, the third page triggers an embedded page loading completion event.

Optionally, reading the target data originating from the second root domain name from the storage space by the first page includes:

The first page reads the target data originating from the second root domain name from the storage space when the first page monitors the loading completion event of the embedded page.

According to another aspect of the present invention, a web page cross-domain communication device is provided, including a first page, a second page, and a third page;

The first page includes an embedded loading module;

The embedded loading module is used to load the second page with the second root domain name in an embedded manner in the first page on the first page with the first root domain name;

The second page includes a data adding module and a page jump module;

The data adding module is used for the second page to add the target data originating from the second root domain name to the preset third page, where the root domain name of the third page is the first root domain name;

The page jump module is configured to jump to the third page;

The third page includes a data extraction module and a data storage module;

The data extraction module is used to extract the contained target data originating from the second root domain name;

The data storage module is used to store the data in a storage space accessible by pages with the first root domain name;

The first page also includes a data reading module;

The data reading module is used for the first page to read the target data originating from the second root domain name from the storage space.

Optionally, the embedded loading module includes:

A data processing request sending submodule, configured for the first page to send a data processing request to the second server corresponding to the second root domain name;

The second page loading submodule is configured to load the page address of the second page from the embedded page preset in the first page after sending the data processing request to obtain the second page.

Optionally, the first page includes a form element, the target source address of the form element is the page address of the second page, and the embedded page is preset in the form element.

Optionally, the data processing request sending submodule includes:

The post request sending subunit is used for the form element of the first page to send a post request for uploading data to the second server to the second server, and the post request carries the data requested to be processed;

Or, the get request sending subunit is used for the form element of the first page to send a get request for obtaining data from the second server to the second server, where the get request carries the data requested to be processed.

Optionally, the second page loading submodule is specifically used to load the target source address of the form element to the embedded page in the form element to obtain the second page.

Optionally, the target data includes all data processing results, partial data processing results, or attribute information of the data processing results obtained from the data processing request sent by the server corresponding to the second root domain name for the first page.

Optionally, the data adding module is specifically used for the second page to correspond to the storage address of the first server corresponding to the first root domain name or the storage address of the second server according to the target data and the first The page address of the third page of the root domain name organization;

The page jumping module is specifically used for jumping the second page to the third page according to the organized page address.

Optionally, the data extraction module includes:

A storage address extraction submodule, configured to extract the target data originating from the second root domain name from the page address of the third page;

The server data extraction submodule is configured to extract target data from the first server or the second server according to the storage address.

Optionally, the data saving module is specifically configured to save the target data originating from the second root domain name in a local storage space divided for the first root domain name and identified by the first root domain name ;

Or, the data saving module is specifically configured to save the target data originating from the second root domain name to a local storage space as a file, and record the file name of the target data in the file directory.

Optionally, the third page also includes:

An event triggering module, configured to trigger an embedded page loading completion event on the third page after saving the target data to the storage space accessible by the page with the first root domain name, or after the loading of the third page is completed .

Optionally, the data reading module is specifically configured to read the target data originating from the second root domain name from the storage space when the first page monitors the loading completion event of the embedded page.

According to the embodiment of the present invention, the first page with the first root domain name loads the second page with different sources and different second root domain names in an embedded manner, and the second page adds the target data obtained from the second root domain name to the In the third page with the first root domain name, and jump to the third page, the third page has the same first root domain name as the first page, and the third page can save the target data to the first root domain name to be accessible storage space, the first page can directly read the target data from the storage space to the second page, which solves the communication problem between cross-domain webpages in the browser, and can realize cross-domain file transfer, data sharing and data synchronization , while reducing development costs and reducing the mutual nesting problem between different root domain names.

Wherein, the target data may be the storage address of the data required by the first page in the server. By adding the storage address to the third page, the data can be read from the server according to the storage address, so that the data of the data required by the first page The amount is not limited to the ability to save data on the third page, which greatly increases the data transmission capacity between cross-domain web pages, and can basically meet all cross-domain data transmission tasks by increasing the megabytes of server storage space.

The above description is only an overview of the technical solution of the present invention. In order to better understand the technical means of the present invention, it can be implemented according to the contents of the description, and in order to make the above and other purposes, features and advantages of the present invention more obvious and understandable , the specific embodiments of the present invention are enumerated below.

Description of drawings

Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiment. The drawings are only for the purpose of illustrating a preferred embodiment and are not to be considered as limiting the invention. Also throughout the drawings, the same reference numerals are used to designate the same parts. In the attached picture:

FIG. 1 shows a flowchart of a webpage cross-domain communication method according to an embodiment of the present invention;

FIG. 2 shows a flow chart of a webpage cross-domain communication method according to another embodiment of the present invention;

Fig. 3 shows a structural block diagram of a web page cross-domain communication device according to an embodiment of the present invention

Fig. 4 shows a structural block diagram of an apparatus for webpage cross-domain communication according to another embodiment of the present invention.

Detailed ways

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided for more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

Example 1

Referring to FIG. 1 , it shows a flowchart of a webpage cross-domain communication method according to an embodiment of the present invention, and the method may specifically include the following steps:

Step 11. The first page with the first root domain name loads the second page with the second root domain name in an embedded manner in the first page.

In the embodiment of the present invention, the first page and the second page are webpages of different sources, that is, their webpage addresses have different root domain names. For example, the webpage address of the first page is www.so.com, and the corresponding first The root domain name is so.com, the webpage address of the second page is www.i.so.com, and the corresponding second root domain name is i.so.com.

Loading the second page in an embedded manner in the first page can be in any achievable manner, for example, by embedding an iframe frame, inserting "<IFRAME name="XXX" width= X height＝X frameborder＝0 src="XXX.htm"></IFRAME>" statement; or use Scriptlets component technology to insert "<OBJECT style="border:0px"type ="text/x-scriptlet"data="XXX.htm"width=X Height=X></OBJECT>" statement; or use script file technology to achieve embedding in sub-pages by introducing external script files into the host page purpose etc.

Step 12, the second page adds the target data from the second root domain name to the preset third page, and jumps to the third page, the root domain name of the third page is the first root domain name.

The second page can obtain target data from the second root domain name. Based on the same-origin policy, the first page with a different root domain name from the second page cannot target data from the second page. After the second page acquires the target data, the target data is added to the preset third page, so that the third page acquires the aforementioned target data.

The second page jumps to the third page (302 jump), and the third page is a subpage embedded in the first page. Since the third page has the same root domain name as the first page, the first page and the third page is the same origin page.

In the embodiment of the present invention, the target data is added to the third page, which may be added to the page content, page address, or related attribute information of the second page, or any other practicable manner.

Wherein, the second page can obtain the target data originating from the second root domain name in any feasible way, for example, the target data can be preset and saved in advance, and the second page can temporarily receive it from the server corresponding to the second root domain name or The target data is requested, or the target data is page content or attribute information of the second page, and the target data can be extracted from the second page.

Step 13. The third page extracts the included target data originating from the second root domain name, and saves it in a storage space accessible to pages with the first root domain name.

A storage space is preset for the first root domain name, which is only accessible to pages with the first root domain name, and the third page saves the target data contained in it to the preset storage space for other pages with the first root domain name Page access target data.

Specifically, the third page may output a script preset on the page, and the script performs an operation of extracting and saving the target data.

Step 14, the first page reads the target data originating from the second root domain name from the storage space.

The first page can access the storage space corresponding to the above-mentioned first root domain name, and can directly read the target data from the storage space, that is, read the target data of the second page. Therefore, the problem between cross-domain web pages in the browser is solved. For communication issues, cross-domain file transfer, data sharing, and data synchronization can be realized, while development costs are reduced, and mutual nesting problems between different root domain names are reduced.

In the embodiment of the present invention, preferably, the step 11 may include:

Sub-step 111, the first page sends a data processing request to the second server corresponding to the second root domain name.

Sub-step 112, after sending the data processing request, the embedded page preset in the first page loads the page address of the second page to obtain the second page.

The first page first requests the second server corresponding to the second root domain name to process data, and further loads the second page with the second root domain name. The embedded page is preset in the first page and points to the page address of the second page. During the loading of the first page, when the embedded page is loaded, the embedded page loads the page address of the second page to obtain the second page.

The preset embedded page may be an iframe subpage, and an iframe is an HTML (HyperTextMark-up Language, hypertext markup language) tag that creates an inline frame containing another document, that is, an inline frame. An iframe subpage is created in the first page, and the page address it points to is the page address of the second page, and the second page can be obtained by loading the iframe subpage. Write the element <iframe src="the address of the webpage to be embedded" width="the width of the subpage" height="height"></iframe> in the webpage. The iframe subpage preset here can be a blank page to avoid consuming computer resources for page loading.

Further preferably, the embedded page can be preset in a page element, and can be preset in different page elements according to actual needs, for example, a form element, an area element, an address element, and the like. In the embodiment of the present invention, preferably, the first page contains a form element, and the embedded page can be set in the form element of the first page.

Correspondingly preferably, the data processing request can be triggered by the form element, and the record of the second page can be further controlled by the form element. Specifically, the sub-step 111 may include:

Sub-step 111-1, the form element of the first page sends a post request to the second server to upload data to the second server, and the post request carries the data requested to be processed.

Or, in sub-step 111-2, the form element of the first page sends a get request to the second server to obtain data from the second server, and the get request carries the data requested to be processed.

Form provides two ways of data transmission, through get request and through post request. Although they are both ways of submitting data, they are quite different in actual transmission.

Post is used to transfer data to the server, and the form element sends a post request for uploading data to the second server; get request is used to obtain data from the server, and the form element sends a get request for obtaining data to the second server.

In contrast, the method of post request is more preferred, the main reasons are:

1. The method of post request is to put the data processed by the request in the form into the data body of the form, and transfer it to the URL pointed to by the action according to the way of corresponding variables and values. In the get request method, the data requested in the form is added to the URL pointed to by the action in the form of variable=value, and the two are connected by "?", and the variables are connected by "&".

2. The security of the get request method is low, because during the transmission process, the data is placed in the URL of the request, and many existing servers, proxy servers or user agents will record the request URL in the log file, and then put Somewhere, so that some private information may be seen by third parties. In addition, the user can also directly see the submitted data on the browser, and some internal system information will be displayed in front of the user. All operations in the post request mode are invisible to the user.

3. Due to the limitation of the URL length, the amount of data transmitted by the get request method is small; and the post request method can transmit a large amount of data, so only post can be used for uploading files.

4. Get restricts the value of the data set of the Form form to be ASCII characters; while post supports the entire ISO10646 character set, which is suitable for more application scenarios.

Correspondingly preferably, the sub-step 112 may include:

Sub-step 112-1, the embedded page in the form element loads the target source address of the form element to obtain the second page.

The target source address of the form element is set as the page address of the second page, and when the second page is rendered to the form element, the form element controls the embedded page to load the page address to obtain the second page.

Correspondingly preferably, the target data may include all data processing results obtained from the data processing request sent by the server corresponding to the second root domain name for the first page, part of the data processing results, or attribute information of the data processing results .

The second page adds the target data from the second root domain name to the preset third page, which can be adding the target data to the third page or the page address of the third page; Adding the storage address of the server to the third page or the page address of the third page can increase the data volume of the transmitted data in this way. Preferably, the step 12 can include:

Sub-step 121, the second page corresponds to the storage address of the first server or the second server corresponding to the first root domain name and the page address of the third page organized by the first root domain name according to the target data .

Sub-step 122, the second page jumps to the third page according to the page address of the organization.

The target data can be stored in the first server corresponding to the first root domain name or in the second server corresponding to the second root domain name, and corresponding to a storage address, the target data can be extracted from the server according to the storage address. The storage address is combined with the first root domain name to organize the page address of the third page, and the obtained root domain name of the page address of the third page is the first root domain name, so that the third page has the same origin as the first page.

After organizing the page address of the third page, the second page can directly jump to the page address to obtain the third page.

Correspondingly preferably, the target data derived from the second root domain name included in the extraction of the third page in step 13 may include:

Sub-step 131, the third page extracts the storage address corresponding to the target data originating from the second root domain name from the page address of the third page.

Sub-step 132, extracting target data from the first server or the second server according to the storage address.

The storage address of the target data is organized in the page address of the third page, and then the storage address of the target data can be directly extracted from the page address, which is simple and convenient, and the data can be read directly from the server according to the storage address, so that the first page needs The amount of data is not limited to the ability to save data on the third page, which greatly increases the data transmission capacity between cross-domain web pages, and can basically meet all cross-domain data transmission tasks by increasing the megabytes of server storage space.

Wherein, saving to the storage space accessible to the page with the first root domain name described in step 13 includes:

Sub-step 133: Save the target data from the second root domain name in a local storage space that is divided for the first root domain name and identified by the first root domain name.

Or, in sub-step 134, save the target data originating from the second root domain name to a local storage space as a file, and record the file name of the target data in the file directory.

Different storage spaces can be allocated for different root domain names, which are identified by each root domain name. For example, Localstorage storage. In HTML5, local storage is a window attribute, including localStorage (local storage) and sessionStorage (session storage), sessionStorage is only accompanied by the session, once the window is closed, it will disappear, and Localstorage is used for persistent local storage, which has the characteristics of block storage according to the root domain name, no active deletion, never expires, and mega-level storage capabilities.

Or assign different files for storing target data for different root domain names, and save a file directory in the storage space, and record the names of each file in the file directory, such as Userdata storage. The local storage space opened up in the system is stored in the unit of file directory, which can be applied in the combined environment of Windows system and IE browser.

To sum up, according to the embodiment of the present invention, the first page with the first root domain name loads the second page with a different source and a different second root domain name in an embedded manner, and the second page will be obtained from the second root domain name Add the target data to the third page with the first root domain name, and jump to the third page. The third page has the same first root domain name as the first page, and the third page can save the target data to the third page. A storage space accessible by a domain name, the first page can directly read the target data of the second page from this storage space, which solves the communication problem between cross-domain web pages in the browser, and can realize cross-domain transfer of files, Data sharing and synchronizing data, while reducing development costs, and reducing mutual nesting problems between different root domain names.

Wherein, the target data may be the storage address of the data required by the first page in the server. By adding the storage address to the third page, the data can be read from the server according to the storage address, so that the data of the data required by the first page The amount is not limited to the ability to save data on the third page, which greatly increases the data transmission capacity between cross-domain web pages, and can basically meet all cross-domain data transmission tasks by increasing the megabytes of server storage space.

Example 2

Referring to FIG. 2 , it shows a flowchart of a webpage cross-domain communication method according to another embodiment of the present invention, and the method may specifically include the following steps:

Step 21: The first page with the first root domain name loads the second page with the second root domain name in an embedded manner in the first page.

Step 22, the second page adds the target data from the second root domain name to the preset third page, and jumps to the third page, the root domain name of the third page is the first root domain name.

Step 23, the third page extracts the included target data originating from the second root domain name, and saves it in a storage space accessible to pages with the first root domain name.

Step 24: After the target data is saved in the storage space accessible by the page with the first root domain name, or after the loading of the third page is completed, the third page triggers an embedded page loading completion event.

Step 25, when the first page monitors the loading completion event of the embedded page, reads the target data originating from the second root domain name from the storage space.

Different from the previous embodiment, in this embodiment, it can be set to save the target data to the accessible storage space set for the first root domain name, or automatically trigger the onload of the iframe after the third page is loaded Event, the onload event is an event that is executed after the page is loaded. The first page can be monitored to the third page when a page completion event occurs, and the target data is read from the storage space. Since the time for storing data and page jump is extremely short, through This solution can enable the first page to obtain the data obtained from the second root domain name as soon as possible.

In a specific implementation, the function fn can be bound to the onload event of the iframe on the first page, and the onload event of the iframe will call the function fn of the first page, and the function fn controls the acquisition of target data.

To sum up, according to the embodiment of the present invention, the first page with the first root domain name loads the second page with a different source and a different second root domain name in an embedded manner, and the second page will be obtained from the second root domain name Add the target data to the third page with the first root domain name, and jump to the third page. The third page has the same first root domain name as the first page, and the third page can save the target data to the third page. A storage space accessible by a domain name, the first page can directly read the target data of the second page from this storage space, which solves the communication problem between cross-domain web pages in the browser, and can realize cross-domain transfer of files, Data sharing and synchronizing data, while reducing development costs, and reducing mutual nesting problems between different root domain names.

Wherein, the target data may be the storage address of the data required by the first page in the server. By adding the storage address to the third page, the data can be read from the server according to the storage address, so that the data of the data required by the first page The amount is not limited to the ability to save data on the third page, which greatly increases the data transmission capacity between cross-domain web pages, and can basically meet all cross-domain data transmission tasks by increasing the megabytes of server storage space.

In order for those skilled in the art to better understand the present invention, a specific example is used below to illustrate the web page cross-domain communication method described in the embodiment of the present invention, wherein the first page is a page, and the corresponding root domain name is www.so .com, the second page is page b, the corresponding root domain name is i.so.com, and the third page is page c, which has the same origin as page a.

1. Page a has image data to be processed. On page a, a form element is used to send a post/get request carrying image data to the server of i.so.com. The target source of the form element is a blank iframe, and page a binds Determine the function fn.

2. When the post/get request is issued, the iframe will load the b page.

3. The server side of i.so.com receives the post/get request, processes the image data to obtain the image processing result.

4. The b page organizes the URL address according to the storage address of the image processing result returned by the server, and 302 goes to the c page corresponding to the address.

5. Page c outputs the front-end script, the front-end script extracts the image processing result, uses localstorage/userdata to store the image processing result locally, and triggers the onload event of the iframe after success

6. The onload event of the iframe will call the method fn of the previous page a. Using fn, the image processing results saved locally can be obtained. So far, the data communication task between different domain names of www.so.com and i.so.com is completed.

Example 3

Referring to FIG. 3 , it shows a structural block diagram of an apparatus for webpage cross-domain communication according to an embodiment of the present invention, which may specifically include a first page 31 , a second page 32 and a third page 33 .

The first page 31 includes an embedded loading module 311;

The embedded loading module 311 is configured to load a second page with a second root domain name in an embedded manner in the first page on the first page with the first root domain name;

The second page includes a data adding module 321 and a page jump module 322;

The data adding module 321 is used for the second page to add the target data originating from the second root domain name to the preset third page, where the root domain name of the third page is the first root domain name;

The page jump module 322 is configured to jump to the third page;

The third page 33 includes a data extraction module 331 and a data storage module 332;

The data extraction module 331 is configured to extract the included target data originating from the second root domain name;

The data storage module 332 is configured to store the data in a storage space accessible to pages with the first root domain name;

The first page also includes a data reading module 312;

The data reading module 312 is used for the first page to read the target data originating from the second root domain name from the storage space.

In the embodiment of the present invention, preferably, the embedded loading module includes:

A data processing request sending submodule, configured for the first page to send a data processing request to the second server corresponding to the second root domain name;

The second page loading submodule is configured to load the page address of the second page from the embedded page preset in the first page after sending the data processing request to obtain the second page.

In the embodiment of the present invention, preferably, the first page includes a form element, the target source address of the form element is the page address of the second page, and the embedded page is preset in the form element.

In the embodiment of the present invention, preferably, the data processing request sending submodule includes:

The post request sending subunit is used for the form element of the first page to send a post request for uploading data to the second server to the second server, and the post request carries the data requested to be processed;

Or, the get request sending subunit is used for the form element of the first page to send a get request for obtaining data from the second server to the second server, where the get request carries the data requested to be processed.

In the embodiment of the present invention, preferably, the second page loading submodule is specifically used to load the target source address of the form element to the embedded page in the form element to obtain the second page.

In the embodiment of the present invention, preferably, the target data includes all data processing results, partial data processing results, or the data processing results obtained from the data processing request sent by the server corresponding to the second root domain name for the first page. Attribute information for the result.

In the embodiment of the present invention, preferably, the data adding module is specifically used for the second page to correspond to the storage address of the first server corresponding to the first root domain name or the storage address of the second server according to the target data The page address of the third page organized with the first root domain name;

The page jumping module is specifically used for jumping the second page to the third page according to the organized page address.

In the embodiment of the present invention, preferably, the data extraction module includes:

A storage address extraction submodule, configured to extract the target data originating from the second root domain name from the page address of the third page;

The server data extraction submodule is configured to extract target data from the first server or the second server according to the storage address.

In the embodiment of the present invention, preferably, the data saving module is specifically configured to save the target data originating from the second root domain name locally in the first root domain name divided for the first root domain name is the storage space identified;

Or, the data saving module is specifically configured to save the target data originating from the second root domain name to a local storage space as a file, and record the file name of the target data in the file directory.

According to the embodiment of the present invention, the first page with the first root domain name loads the second page with different sources and different second root domain names in an embedded manner, and the second page adds the target data obtained from the second root domain name to the In the third page with the first root domain name, and jump to the third page, the third page has the same first root domain name as the first page, and the third page can save the target data to the first root domain name to be accessible storage space, the first page can directly read the target data from the storage space to the second page, which solves the communication problem between cross-domain webpages in the browser, and can realize cross-domain file transfer, data sharing and data synchronization , while reducing development costs and reducing the mutual nesting problem between different root domain names.

Wherein, the target data may be the storage address of the data required by the first page in the server. By adding the storage address to the third page, the data can be read from the server according to the storage address, so that the data of the data required by the first page The amount is not limited to the ability to save data on the third page, which greatly increases the data transmission capacity between cross-domain web pages, and can basically meet all cross-domain data transmission tasks by increasing the megabytes of server storage space.

Example 4

Referring to FIG. 4 , it shows a structural block diagram of an apparatus for webpage cross-domain communication according to another embodiment of the present invention, which may specifically include a first page 41 , a second page 42 and a third page 43 .

The first page 41 includes an embedded loading module 411;

The embedded loading module 411 is configured to load a second page with a second root domain name in an embedded manner in the first page on the first page with the first root domain name;

The second page includes a data adding module 421 and a page jump module 422;

The data adding module 421 is used for the second page to add the target data originating from the second root domain name to the preset third page, where the root domain name of the third page is the first root domain name;

The page jump module 422 is configured to jump to the third page;

The third page 43 includes a data extraction module 431, a data storage module 432 and an event trigger module 433;

The data extraction module 431 is configured to extract the included target data originating from the second root domain name;

The data saving module 432 is configured to save the data in a storage space accessible to pages with the first root domain name;

The event triggering module 433 is configured to trigger the third page to trigger the completion of loading of the embedded page after the target data is saved to the storage space accessible by the page with the first root domain name, or after the loading of the third page is completed event.

The first page also includes a data reading module 412;

The data reading module 412 is specifically configured to read the target data originating from the second root domain name from the storage space when the first page monitors the loading completion event of the embedded page.

According to the embodiment of the present invention, the first page with the first root domain name loads the second page with different sources and different second root domain names in an embedded manner, and the second page adds the target data obtained from the second root domain name to the In the third page with the first root domain name, and jump to the third page, the third page has the same first root domain name as the first page, and the third page can save the target data to the first root domain name to be accessible storage space, the first page can directly read the target data from the storage space to the second page, which solves the communication problem between cross-domain webpages in the browser, and can realize cross-domain file transfer, data sharing and data synchronization , while reducing development costs and reducing the mutual nesting problem between different root domain names.

Wherein, the target data may be the storage address of the data required by the first page in the server. By adding the storage address to the third page, the data can be read from the server according to the storage address, so that the data of the data required by the first page The amount is not limited to the ability to save data on the third page, which greatly increases the data transmission capacity between cross-domain web pages, and can basically meet all cross-domain data transmission tasks by increasing the megabytes of server storage space.

Since the device embodiment basically corresponds to the method embodiment shown in Figure 1 and Figure 2 above, for details not described in this embodiment, you can refer to the relevant description in the previous embodiment, and will not go into details here .

The algorithms and displays presented herein are not inherently related to any particular computer, virtual system, or other device. Various generic systems can also be used with the teachings based on this. The structure required to construct such a system is apparent from the above description. Furthermore, the present invention is not specific to any particular programming language. It should be understood that various programming languages can be used to implement the content of the present invention described herein, and the above description of specific languages is for disclosing the best mode of the present invention.

In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure the understanding of this description.

Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, in order to streamline this disclosure and to facilitate an understanding of one or more of the various inventive aspects, various features of the invention are sometimes grouped together in a single embodiment, figure, or its description. This method of disclosure, however, is not to be interpreted as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the Detailed Description are hereby expressly incorporated into this Detailed Description, with each claim standing on its own as a separate embodiment of this invention.

Those skilled in the art can understand that the modules in the device in the embodiment can be adaptively changed and arranged in one or more devices different from the embodiment. Modules or units or components in the embodiments may be combined into one module or unit or component, and furthermore may be divided into a plurality of sub-modules or sub-units or sub-assemblies. All features disclosed in this specification (including accompanying claims, abstract and drawings) and any method or method so disclosed may be used in any combination, except that at least some of such features and/or processes or units are mutually exclusive. All processes or units of equipment are combined. Each feature disclosed in this specification (including accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.

Furthermore, those skilled in the art will understand that although some embodiments described herein include some features included in other embodiments but not others, combinations of features from different embodiments are meant to be within the scope of the invention. and form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.

The various component embodiments of the present invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art should understand that a microprocessor or a digital signal processor (DSP) may be used in practice to implement some or all functions of some or all components in the web page cross-domain communication device according to the embodiment of the present invention. The present invention can also be implemented as an apparatus or an apparatus program (for example, a computer program and a computer program product) for performing a part or all of the methods described herein. Such a program for realizing the present invention may be stored on a computer-readable medium, or may be in the form of one or more signals. Such a signal may be downloaded from an Internet site, or provided on a carrier signal, or provided in any other form.

It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention can be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In a unit claim enumerating several means, several of these means can be embodied by one and the same item of hardware. The use of the words first, second, and third, etc. does not indicate any order. These words can be interpreted as names.

Claims (10)

1. a webpage cross-domain communication method, comprising:

The first page possessing the first rhizosphere name loads in the mode embedded second page possessing the second rhizosphere name in described first page;

The target data being derived from the second rhizosphere name is added in the 3rd preset page by described second page, and jumps to described 3rd page, the rhizosphere first rhizosphere name by name of described 3rd page;

Be derived from the target data of the second rhizosphere name described in described 3rd page extraction comprises, and be saved in the addressable memory space of the page possessing the first rhizosphere name;

The target data of the second rhizosphere name is derived from described in described first page reads from described memory space.

2. the method for claim 1, wherein described in possess the first rhizosphere name first page in described first page, load in the mode embedded the second page face possessing the second rhizosphere name comprise:

Described first page sends data processing request to the second server of the second rhizosphere name correspondence;

After the described data processing request of transmission, the embedding page preset in described first page loads the page address of described second page, obtains second page.

3. the method as described in any one of claim 1-2, wherein, comprises Form Element in described first page, and the target source address of described Form Element is the page address of described second page, and the described embedding page is preset in described Form Element.

4. the method as described in any one of claim 1-3, wherein, described first page comprises to the second server transmission data processing request of the second rhizosphere name correspondence:

The post that the Form Element of described first page sends to described second server uploading data to described second server asks, and the data of request process are carried in described post request;

Or the Form Element of described first page sends the get request obtaining data from described second server to described second server, the data of request process are carried in described get request.

5. the method as described in any one of claim 1-4, wherein, the embedding page preset in described first page loads the page address of described second page, obtains second page face and comprises:

The embedding page in described Form Element loads the target source address of described Form Element, obtains second page.

6. the method as described in any one of claim 1-5, wherein, the attribute information of total data result, partial data result or described data processed result that the server that described target data comprises described second rhizosphere name correspondence obtains for the data processing request that described first page sends.

7. the method as described in any one of claim 1-6, wherein, the target data being derived from the second rhizosphere name is added in the 3rd preset page by described second page, and jumps to described 3rd page and comprise:

Described second page is according to the corresponding page address at the described first server of the first rhizosphere name correspondence or the memory address of described second server and described first rhizosphere name tissue the 3rd page of described target data;

Described second page jumps to the 3rd page according to the page address of tissue.

8. the method as described in any one of claim 1-7, wherein, described in be saved in the addressable memory space of the page possessing the first rhizosphere name and comprise:

The described target data being derived from the second rhizosphere name is saved in local that divide for described first rhizosphere name, be called mark with described first rhizosphere memory space;

Or, the described target data being derived from the second rhizosphere name is saved in local memory space in the mode of file, and in file directory, records the file name of described target data.

9. a webpage cross-domain communication device, comprises first page, second page and the 3rd page;

Described first page comprises embedding load-on module;

Described embedding load-on module, loads in the mode embedded second page possessing the second rhizosphere name for the first page possessing the first rhizosphere name in described first page;

Described second page face comprises data and adds module and page jump module;

Described data add module, add in the 3rd preset page for described second page by the target data being derived from the second rhizosphere name, the rhizosphere first rhizosphere name by name of described 3rd page;

Described page jump module, for jumping to described 3rd page;

Described 3rd page comprises data extraction module and data storage module;

Described data extraction module, for extract comprise described in be derived from the target data of the second rhizosphere name;

Described data storage module, for being saved in the addressable memory space of the page possessing the first rhizosphere name;

Described first page also comprises data read module;

Described data read module, is derived from the target data of the second rhizosphere name for described first page from described memory space described in reading.

10. device as claimed in claim 9, wherein, described embedding load-on module comprises:

Data processing request sends submodule, for the second server transmission data processing request of described first page to the second rhizosphere name correspondence;

Second page loads submodule, and for after the described data processing request of transmission, the embedding page preset in described first page loads the page address of described second page, obtains second page.