TWI692232B - Method and device for loading web page based on iframe - Google Patents

Abstract

A method for loading a web page based on iFrame includes the following steps. A mixed content of an HTTPS web page containing an HTTP content is received. When the HTTP content is to be loaded into an iFrame object, it is detected whether the mixed content is blocked by a browser. When the mixed content is not blocked, the HTTP content is loaded into the iFrame object, and the information in the HTTPS web page and the iFrame object are exchanged by an application interface. When the mixed content is blocked, the HTTP content is loaded into a new window object, and the information in the HTTPS web page and the new window object are exchanged by the application interface.

Description

Webpage loading method and device based on embedded window

The invention relates to a webpage loading method, and in particular to a webpage loading method and device based on embedded windows.

With the continuous development of Internet technology, more and more people obtain information and services from web pages, such as browsing news, watching movies, online shopping, etc. The above information and services are often presented to users in the form of web pages. When users browse a web page, they often need to load other web pages (such as embedded windows) to show the user recommended information or prompt information. However, when the webpage content of the embedded window does not comply with the browser's transmission security protocol, the webpage content will be blocked by the browser, so the user cannot successfully obtain the relevant webpage content and services, affecting the user's experience.

The invention relates to a method and a device for loading a webpage based on an embedded window, which can maintain the display and exchange of HTTP content in the HTTPS webpage window to avoid affecting the user's experience.

According to one aspect of the present invention, a web page loading method based on an embedded window is proposed, including the following steps. Acquire a mixed content of an HTTPS web page containing an HTTP content. When HTTP content is to be loaded into an embedded window object, it is detected whether the mixed content is blocked by a browser. When the mixed content is not blocked, the HTTP content is loaded into the embedded window object, and an application program interface is used to exchange messages in the HTTPS web page and the embedded window object. When the mixed content is blocked, the HTTP content is loaded into a new window object, and the information in the HTTPS web page and the new window object is exchanged through the application program interface.

According to one aspect of the present invention, a webpage loading device based on an embedded window is provided, including a mixed content blocking detection module, a browser window object, an HTTP content loading module, and an application program interface. The mixed content blocking detection module is used to obtain a mixed content of an HTTPS webpage including an HTTP content and detect whether the HTTP content is blocked by a browser. The browser window object includes an embedded window object and a new window object. The HTTP content loading module is used to load the HTTP content into the embedded window object or the new window object according to whether the HTTP content is blocked by the browser. The application program interface is used to exchange information in HTTPS web pages and embedded window objects or new window objects.

In order to have a better understanding of the above and other aspects of the present invention, the following examples are specifically described in conjunction with the accompanying drawings as follows:

The following is an example for detailed description. The example is only used as an example, not intended to limit the scope of the present invention. The following description uses the same/similar symbols to indicate the same/similar components. Directional terms mentioned in the following embodiments, for example: up, down, left, right, front or back, etc., are only directions referring to the drawings. Therefore, the directional terminology is used to illustrate rather than limit the invention.

According to an embodiment of the present invention, a webpage loading method based on an embedded window (iFrame) is proposed. The embedded window is an inline frame for creating another webpage. When an external webpage content needs to be embedded in a webpage window, a command code can be inserted in the code for executing the webpage window to connect to the URL address of the external webpage.

In general, an HTTPS web page containing HTTP content can be called mixed content. According to the security level, HTTP content can be divided into passive mixed content (Passive Mixed content) and active mixed content (Active Mixed content). For passive mixed content, the browser generally defaults to displaying only warning messages, but HTTP content can still be loaded and displayed on HTTPS web pages; and for active mixed content, the browser generally defaults to HTTP content not directly on HTTPS web pages Upload and display, especially the HTTP content in the embedded window. Therefore, when the web page of the loaded external window is HTTP content, the browser prohibits the loading of the HTTP content, and thus cannot create another HTTP web page in the current HTTPS web page window.

Since HyperText Transfer Protocol Secure (HTTPS) has higher security than HTTP, in order to improve the security of information exchange, most current browsers require HTTPS webpage windows in addition to certain types of content, It is forbidden to load HTTP content, so the loading content of web pages based on embedded windows will be affected.

Accordingly, the present invention proposes a webpage loading method based on an embedded window, which can maintain the display and message exchange of HTTP content in the HTTPS webpage window to avoid affecting the user experience.

Please refer to FIGS. 1 and 2, according to an embodiment of the present invention, a web page loading method based on an embedded window includes the following steps S11-S14. In step S11, a mixed content of an HTTPS web page including an HTTP content is obtained. In step S12, when an HTTP content is to be loaded into an embedded window object 132, it is detected whether the HTTP content is blocked by a browser. In step S13, when the mixed content is not blocked, the HTTP content is loaded into the embedded window object 132, and an application interface 140 is used to exchange messages in the HTTPS web page and the embedded window object 132. In step S14, when the mixed content is blocked, the HTTP content is loaded into a new window object 134, and the information in the HTTPS web page and the new window object 134 is exchanged by the application program interface 140.

Referring to FIGS. 1 and 2, according to an embodiment of the present invention, a webpage loading device 100 based on an embedded window includes a mixed content blocking detection module 110, an HTTP content loading module 120, a browser window object 130, and a Application program interface 140. The mixed content blocking detection module 110 is used to obtain a mixed content of an HTTPS webpage including an HTTP content, and detect whether the mixed content is blocked by a browser. The browser window object 130 includes an embedded window object 132 and a new window object 134. The HTTP content loading module 120 is used to load the HTTP content into the embedded window object 132 or the new window object 134 according to whether the mixed content is blocked by the browser. The application program interface 140 is used to exchange HTTPS web pages and messages in the embedded window object 132 or the new window object 134.

In steps S11 and 12, the mixed content blocking detection module 110 is used to obtain and determine whether an HTTPS web page containing HTTP content (hereinafter referred to as mixed content) is blocked by a browser, and the detection method is as shown in Figs. 5 and 6 or 7 and 7. As shown in Figure 8, we will explain in detail later.

In step S13, when the mixed content is not blocked by the browser, the HTTP content loading module 120 loads the HTTP content into the embedded window object 132.

Referring to FIG. 3, HTTP content can be loaded in the embedded window object 132, and the embedded window object 132 is displayed in the HTTPS web page window 131. In addition, the application program interface 140 can exchange information in the HTTPS web page and the embedded window object 132 through the business communication module. Therefore, the user can successfully obtain HTTP content and related services from the embedded window object 132.

In addition, in step S14, when the mixed content is blocked by the browser, the HTTP content loading module 120 cannot load the HTTP content into the embedded window object 132. At this time, the HTTP content loading module 120 loads the HTTP content into a new window object 134. In this embodiment, the new window object 134 is, for example, a pop-up window opened by Window.open or a new tab. The code examples are as follows: <script LANGUAGE=“javascript”>window.open ('page.html', 'newwindow','height=100, width=400, top=0, left=0, toolbar=no, menubar=no, scrollbars=no, resizable=no, location=no, status=no') //…＜ /script＞

Referring to FIG. 4, HTTP content can be loaded in a new window object 134, and the new window object 134 and the HTTPS web window 131 object are two different window objects. In addition, the application program interface 140 can exchange information in the HTTPS web page and the new window object 134 through the business communication module. Therefore, the user can successfully obtain HTTP content and related services from the new window object 134.

In this embodiment, the business communication module exchanges messages with the embedded window object 132 or the new window object 134, which can be accomplished using Window.postMessage of W3C specification. Window.postMessage is an application program interface 140 that can be used to communicate the content of one window with the content of another window to complete the communication between the HTTPS web page and the HTTP content. The code examples are as follows: //Pop up a new window var domain = 'http://scriptandstyle.com'; var myPopup = window.open(domain ), + +//windowPostMessageListener.html','myWindow'); // Periodically send message messages setInterval(function(){ var message ='Hello ! The time is: '+ (new Date().getTime()); console.log('blog.local: sending message:' + message); // send the message and target URI myPopup.postMessage(message,domain ); },6000);

Please refer to FIGS. 5 and 6, wherein FIG. 5 shows a schematic diagram of the mixed content blocking detection module 110 for determining whether the mixed content is blocked by a browser, and FIG. 6 shows a diagram for determining whether the mixed content is blocked by a browser in FIG. 5 Schematic diagram of the device blocking process.

Referring to FIG. 5, the mixed content blocking detection module 110 includes a loading completion event listener 112 and a loading timeout monitoring unit 114. The loading completion event listener 112 is used to listen to whether a loading completion event is triggered. For example, when the webpage of the window is an HTTP webpage, the webpage loaded with the embedded element 133 (eg, <iFrame> element) can normally trigger a loading completion event. However, when the webpage of the window is an HTTPS webpage, the webpage loaded with the embedded element 133 will be blocked by the browser, so a successful loading event will not be triggered. Therefore, when loading HTTP content with the embedded element 133, the loading timeout monitoring unit 114 can determine the current state of the browser according to whether a loading success event is triggered. The above-mentioned HTTP content loaded with the embedded element 133 may be the HTTP content expected to be loaded or the HTTP content in a URL specifically used for detection.

Please refer to Figures 5 and 6 together, the determination process includes S21-S24. First, in step S21, when loading an HTTP content with the embedded element 133, because the HTTP content is blocked on the HTTPS website by the browser, a loading success event cannot be generated. Therefore, in step S23, if the load timeout monitoring unit 114 determines that the load has timed out without a load success event, the browser is marked as a state where mixed content is blocked. On the contrary, the loading of HTTP content will not be blocked by the browser on the HTTP website. Therefore, in step S24, if the loading timeout monitoring unit 114 determines that the loading did not time out and a successful loading event occurs, the browser is marked as a state where mixed content is allowed .

Next, please refer to FIGS. 7 and 8, wherein FIG. 7 illustrates a schematic diagram of the mixed content blocking detection module 110 for determining whether the mixed content is blocked by a browser in another embodiment, and FIG. 8 illustrates the FIG. 7 Schematic diagram of a process for determining whether mixed content is blocked by a browser.

Referring to FIG. 7, the mixed content blocking detection module 110 includes a network request module 113, a request error event listener 115, and an error type interpretation unit 117. The network request module 113 is used to initiate a request to an HTTP URL. The request error event listener 115 is used to listen to whether there is a request error event. For example, when the browser does not set a blocking mechanism, the network request module 113 can successfully initiate a request to the HTTP URL. However, when the browser sets the blocking mechanism, the request to the HTTP URL will be blocked by the browser and a request error event will be generated. Therefore, the error type interpretation unit 117 can determine the current state of the browser according to whether a request error event is generated. In an embodiment, the HTTP URL may be the URL of the HTTP content expected to be loaded, or an HTTP URL specifically used for detection.

Please refer to Figures 7 and 8 together, the determination process includes S31-S34. First, in step S31, the network request module 113 initiates a request to an HTTP URL. In step S32, if the error type interpretation unit 117 determines that the request is blocked by the browser and a request error event is generated, then in step S33, the browser is marked as a state in which mixed content is blocked. Conversely, in step S32, when the request to the HTTP website is not blocked by the browser, then in step S34, the browser is marked as a state that allows mixed content.

In addition, in another embodiment, when a mixed content blocking detection module 110 is provided in the browser, the state data can be directly retrieved from the mixed content blocking detection module 110 to determine whether the browser is in the state of blocking mixed content or The state that allows mixed content. In addition, when the blocking mechanism of the browser allows the user to close by himself, the loading method of the present invention can still maintain the display and exchange of HTTP content in the HTTPS web page window 131 to avoid affecting the user experience. If the blocking mechanism of the browser does not allow the user to close itself, the HTTP content is loaded in a new window. In addition, the new window can be set to close after the loading operation is completed, so that it does not affect the user's operation on the main webpage window.

In summary, although the present invention has been disclosed as above with examples, it is not intended to limit the present invention. Those with ordinary knowledge in the technical field to which the present invention belongs can make various modifications and retouching without departing from the spirit and scope of the present invention. Therefore, the scope of protection of the present invention shall be deemed as defined by the scope of the attached patent application.

100: Webpage loading device based on embedded window 110: Mixed content blocking detection module 112: Load completed event listener 113: Network request module 114: Load timeout monitoring unit 115: Request error event listener 117: Error type interpretation unit 120: HTTP content loading module 130: Browser window object 131: HTTPS web window 132: Embedded window object 134: New window object 140: Application program interface S11-S14, S21-S24, S31-S34: steps

FIG. 1 is a schematic diagram of a web page loading method based on an embedded window according to an embodiment of the invention. FIG. 2 is a schematic diagram of a webpage loading device based on an embedded window according to an embodiment of the invention. FIG. 3 shows a schematic diagram of the embedded window object displayed in the HTTPS webpage window. FIG. 4 shows a schematic diagram of loading HTTP content in a new window object. FIG. 5 is a schematic diagram of a mixed content blocking detection module for determining whether mixed content is blocked by a browser. FIG. 6 is a schematic flowchart of determining whether the mixed content is blocked by a browser in FIG. 5. FIG. 7 is a schematic diagram of a mixed content blocking detection module for determining whether mixed content is blocked by a browser in another embodiment. FIG. 8 is a schematic flowchart of determining whether the mixed content is blocked by a browser in FIG. 7.

S11-S14: various steps

Claims (12)

A web page loading method based on an embedded window, including: obtaining a mixed content of an HTTPS web page including an HTTP content; when the HTTP content is to be loaded into an embedded window object, detecting whether the mixed content is browsed Blocking; when the mixed content is not blocked, loading the HTTP content in the embedded window object, and exchanging messages in the HTTPS web page and the embedded window object with an application interface; and when the mixed content When blocked, the HTTP content is loaded into a new window object, and the application program interface is used to exchange messages in the HTTPS web page and the new window object. The method as described in item 1 of the patent application scope, wherein the step of detecting whether the mixed content is blocked by a browser includes: loading the HTTP content with an embedded element; determining whether a successful loading event occurs in the browser; when If the loading has timed out without the loading success event, the browser is marked as blocking the mixed content; and when the loading has not timed out and the loading success event occurs, the browser is marked with the mixed content allowed state. The method as described in item 1 of the patent application scope, wherein the step of detecting whether the mixed content is blocked by a browser includes: initiating a request to an HTTP URL; determining that the request is blocked by the browser and generating a request error event , Mark the browser as a state that blocks the mixed content; and determine that the request is not blocked by the browser, mark the browser as a state that allows the mixed content. The method as described in item 1 of the patent application scope, wherein the step of detecting whether the mixed content is blocked by a browser includes directly obtaining status data from a blocking detection module in the browser. The method as described in item 1 of the patent application scope, wherein the application program interface exchanges information in the HTTPS web page and the embedded window object through a business communication module. The method as described in item 1 of the patent application scope, wherein the application program interface exchanges information in the HTTPS web page and the new window object through a business communication module. A webpage loading device based on an embedded window includes: a mixed content blocking detection module for acquiring a mixed content of an HTTPS webpage including an HTTP content, and detecting whether the mixed content is blocked by a browser; Browser window object, including an embedded window object and a new window object; an HTTP content loading module for loading the HTTP content in the embedded window object according to whether the mixed content is blocked by the browser or In the new window object; and an application program interface for exchanging messages in the HTTPS webpage and the embedded window object or the new window object. The device as described in item 7 of the patent application scope, wherein the mixed content blocking detection module includes: a load completion event listener to listen to whether a load completion event is triggered when the HTTP content is loaded with an embedded element; and A loading timeout monitoring unit, judging that the loading has timed out without the loading success event, marking the browser as blocking the mixed content, or judging that the loading has not timed out and the loading success event occurred, marking the browser as The state of the mixed content is allowed. The device as described in item 7 of the patent application scope, wherein the mixed content blocking detection module includes: a network request module that initiates a request to an HTTP URL; a request error event listener; and an error type determination Unit, determining that the request is blocked by the browser and generating a request error event, marking the browser as blocking the mixed content, or determining that the request is not blocked by the browser, marking the browser as allowing the mixed content status. The device as described in item 7 of the patent application scope, wherein the mixed content blocking detection module is directly provided in the browser. The device as described in item 7 of the patent application scope, wherein the application program interface exchanges information in the HTTPS web page and the embedded window object through a business communication module. The device as described in item 7 of the patent application scope, wherein the application program interface exchanges information in the HTTPS web page and the new window object through a business communication module.

Images