Webpage jumping method compatible with different browsers and related equipment thereof

Abstract

The invention relates to the technical field of browser information processing, and provides a webpage skipping method compatible with different browsers and a related device thereof.The webpage skipping method includes the steps that a webpage skipping request initiated by a user side is received, and the webpage skipping request is used for requesting a current webpage to skip from a first browser to a second browser for operation; the first browser runs a current webpage before the webpage jump request is initiated, information of a user-side operating system is obtained to judge whether the user-side operating system supports a user-defined jump protocol, the user-defined jump protocol is that the current webpage jumps from the first browser to a second browser, and when the user-side operating system supports the user-defined jump protocol, the current webpage jumps from the first browser to the second browser. And the current webpage is controlled to jump from the first browser to the second browser for operation, so that the user experience is improved, and the server overhead is reduced.

Description

Technical Field

[0001] The present invention relates to the technical field of browser information processing, and more specifically to a web page jump method compatible with different browsers and related equipment. Background Art

[0002] In practice, different browsers have different parsing and rendering capabilities for the same web page, and it is often necessary to redirect the same web page between different browsers. For example, redirecting the same web page between different browsers can test the compatibility of web pages under different browsers and help developers discover and solve problems in a timely manner. For another example, some web pages may not be displayed normally or the user experience is poor under certain browsers. At this time, it is possible to automatically redirect to other browsers under certain browsers to improve the user experience. For another example, some websites or applications may only support specific browsers. When opening them under other browsers, users will be prompted to switch to supported browsers. This method can help websites or applications promote and market themselves and provide better user experience when users use supported browsers. At present, browser identification and redirection technology is mainly used to redirect the same web page between different browsers. By detecting the type and version of the browser used by the user, the browser used by the user is redirected to a suitable web page or application based on this information. Although browser identification and redirection technology can be used to redirect the same web page between different browsers, automatic redirection may cause unnecessary trouble or confusion to users, especially problems such as screen flashing or delays may occur during the redirection process, affecting the user experience. In addition, browser identification and redirection technology needs to be processed on the server, which may increase the burden on the server. Especially in high concurrency situations, it may cause the server to respond more slowly or even crash.

[0003] In summary, the existing web page jump technology between different browsers has technical problems such as poor user experience and increased server overhead. Summary of the invention

[0004] The technical problem to be solved by the present invention is to provide a web page jump method and related equipment compatible with different browsers to improve user experience and reduce server overhead in view of the shortcomings of the above technical solutions.

[0005] In a first aspect, the present invention provides a web page jump method compatible with different browsers, wherein the web page jump method compatible with different browsers is run on a server, and the web page jump method compatible with different browsers comprises the following steps:

[0006] S1. Receive a web page jump request initiated by a user terminal, wherein the web page jump request is a request for a current web page to jump from a first browser to a second browser for execution, and the first browser executes the current web page before the web page jump request is initiated;

[0007] S2, obtaining the user-side operating system information to determine whether the user-side operating system supports a custom jump protocol, where the custom jump protocol is for jumping the current web page from the first browser to the second browser;

[0008] S3. When the user-side operating system supports a custom jump protocol, control the current webpage to jump from the first browser to the second browser for execution.

[0009] Further, after obtaining the user-side operating system information to determine whether the user-side operating system supports the custom jump protocol, the method further includes:

[0010] When the user's operating system does not support the custom jump protocol, the user is prompted to download and install the custom jump protocol registration tool;

[0011] The completion confirmation information of the installation of the custom jump protocol registration tool by the user end is detected, and when the completion confirmation information is detected, the current webpage is controlled to jump from the first browser to the second browser for execution.

[0012] Further, after the detection of the completion confirmation information of the user end for the installation of the custom jump protocol registration tool, it also includes:

[0013] When the completion confirmation information is not detected, the user terminal is prompted to download and install a custom jump protocol registration tool.

[0014] Further, the determining whether the user-side operating system supports the custom jump protocol includes:

[0015] Creating a hidden iframe element, the style of the iframe element is not displayed on the web page;

[0016] Add the iframe element to the page of the webpage, and set the address of the iframe element to the set protocol address to indicate loading a blank page;

[0017] When the address of the iframe element is successfully set to the set protocol address, it is determined that the user-side operating system supports the custom jump protocol. When the address of the iframe element is failed to be set to the set protocol address, it is determined that the user-side operating system does not support the custom jump protocol.

[0018] Further, after determining that the user-side operating system does not support the custom jump protocol, the method includes:

[0019] Generate a prompt pop-up box indicating that the user-side operating system does not support the custom jump protocol;

[0020] Control the display of the prompt pop-up box to prompt the user at the user end.

[0021] Furthermore, the set protocol address is about:blank.

[0022] Further, the style of the iframe element is set to display:none, or the style of the iframe element is set to visibility:hidden to hide the style of the iframe element.

[0023] Furthermore, the first browser is IE browser, and the second browser is Chrome browser.

[0024] In a second aspect, the present invention provides a web page jump device compatible with different browsers, comprising:

[0025] A web page jump request receiving module, used to receive a web page jump request initiated by a user terminal, wherein the web page jump request is a request for a current web page to jump from a first browser to a second browser for execution, and the first browser executes the current web page before the web page jump request is initiated;

[0026] A custom jump protocol support judgment module is used to obtain the user-side operating system information to determine whether the user-side operating system supports the custom jump protocol, wherein the custom jump protocol is for the current web page to jump from the first browser to the second browser;

[0027] The current web page jump control module is used to control the current web page to jump from the first browser to the second browser when the user-side operating system supports a custom jump protocol.

[0028] In a third aspect, the present invention provides a server comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the web page jump method compatible with different browsers as described in any one of claims 1 to 8 when executing the computer program.

[0029] Compared with the prior art, the present invention has the following beneficial effects:

[0030] The web page jump method and related devices compatible with different browsers provided by the present invention receive a web page jump request initiated by a user end, wherein the web page jump request is a request for a current web page to jump from a first browser to a second browser for execution, the first browser executes the current web page before the web page jump request is initiated, and the user end operating system information is obtained to determine whether the user end operating system supports a custom jump protocol, wherein the custom jump protocol is for the current web page to jump from the first browser to the second browser, and when the user end operating system supports the custom jump protocol, the current web page is controlled to jump from the first browser to the second browser for execution, thereby improving user experience and reducing server overhead. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1 It is a flow chart of a web page jump method compatible with different browsers of the present invention;

[0032] Figure 2 It is a schematic diagram of the structure of the web page jump device compatible with different browsers of the present invention;

[0033] Figure 3 It is a schematic diagram of the architecture of the web page jump system compatible with different browsers of the present invention;

[0034] Figure 4 It is a schematic diagram of the architecture of the server of the present invention. DETAILED DESCRIPTION

[0035] In order to make the purpose, technical solution and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention.

[0036] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the numbers used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein.

[0037] Embodiment 1

[0038] See also Figure 1-Figure 4Embodiment 1 provides a web page jump method compatible with different browsers, and the web page jump method compatible with different browsers includes steps S1, S2, and S3, by receiving a web page jump request initiated by a user terminal, the web page jump request is a request for a current web page to jump from a first browser to a second browser for execution, the first browser runs the current web page before the web page jump request is initiated, and the user terminal operating system information is obtained to determine whether the user terminal operating system supports a custom jump protocol, the custom jump protocol is for the current web page to jump from the first browser to the second browser, and when the user terminal operating system supports the custom jump protocol, the current web page is controlled to jump from the first browser to the second browser for execution, thereby improving user experience and reducing server overhead.

[0039] It should be noted that the web page jump method compatible with different browsers provided in this embodiment can be run on a server. As the execution subject of all or part of the steps in the web page jump method compatible with different browsers, the server can execute steps S1, S2 and S3 in this embodiment, and can also run some or all of the steps of the method involved below. It should be noted that the server includes a memory, a processor, and a network interface that communicate with each other through a system bus. It should be pointed out that only some components of the server are shown in the figure, but it should be understood that it is not required to implement all the components shown, and more or fewer components can be implemented instead. Among them, it can be understood by technicians in this technical field that the server here is a device that can automatically perform numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes but is not limited to microprocessors, application specific integrated circuits (Application Specific Integrated Circuit, ASIC), programmable gate arrays (Field-Programmable Gate Array, FPGA), digital processors (Digital Signal Processor, DSP), embedded devices, etc. The server can interact with the user through a keyboard, mouse, remote control, touchpad or voice control device. The memory includes at least one type of readable storage medium, and the readable storage medium includes flash memory, hard disk, multimedia card, card-type memory (for example, SD or DX memory, etc.), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, disk, optical disk, etc. In some embodiments, the memory can be an internal storage unit of the server, such as a hard disk or memory of the server. In other embodiments, the memory can also be an external storage device of the server, such as a plug-in hard disk equipped on the server, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. Of course, the memory can also include both the internal storage unit of the server and its external storage device.

[0040] Specifically, in step S1, the server receives a web page jump request initiated by a user terminal, wherein the web page jump request is a request for a current web page to jump from a first browser to a second browser for execution, and the first browser executes the current web page before the web page jump request is initiated.

[0041] It should be noted that the first browser may be IE browser, and the second browser may be Chrome browser. It is understandable that the first browser may also be other browsers besides IE browser, and the second browser may also be other browsers besides Chrome browser.

[0042] It should be noted that the user end can be a mobile intelligent terminal, such as a smart phone. It is understandable that the user end can also be a PC. Among them, the user end requests that the current web page jump from the first browser to the second browser to run, which has multiple practical significances. For example, jumping the same web page between different browsers can test the compatibility of the web page under different browsers, helping developers to discover and solve problems in a timely manner. For another example, some web pages may not be displayed normally or the user experience may be poor under certain browsers. At this time, it can automatically jump to other browsers under certain browsers to improve the user experience. For another example, some websites or applications may only support specific browsers. When opening them in other browsers, users will be prompted to switch to supported browsers. This method can help websites or applications promote and market themselves, and provide better user experience when users use supported browsers.

[0043] Specifically in step S2, the server obtains the user-side operating system information to determine whether the user-side operating system supports a custom jump protocol, where the custom jump protocol is for the current web page to jump from the first browser to the second browser.

[0044] It should be noted that in this step, the server obtains the user-side operating system information to determine whether the user-side operating system supports a custom jump protocol. The custom jump protocol is for the current web page to jump from the first browser to the second browser. This method does not require modifying the structure of the web page, nor does it increase the burden on the user side. It can cope with different browsers and operating systems, which is flexible and convenient.

[0045] In some preferred embodiments, after obtaining the user-side operating system information to determine whether the user-side operating system supports the custom jump protocol, the following steps may also be included: when the user-side operating system does not support the custom jump protocol, prompting the user-side to download and install the custom jump protocol registration tool; detecting the completion confirmation information of the user-side completing the installation of the custom jump protocol registration tool, and when the completion confirmation information is detected, controlling the current web page to jump from the first browser to the second browser to run.

[0046] It should be noted that, in this embodiment, the user only needs to download and install the custom jump protocol registration tool according to the prompts. The server will automatically detect the completion confirmation information of the user terminal on the completion of the installation of the custom jump protocol registration tool. When the completion confirmation information is detected, the current web page is controlled to jump from the first browser to the second browser for execution. This method does not require modifying the structure of the web page, nor does it increase the burden on the user terminal. It can cope with different browsers and operating systems, which is flexible and convenient.

[0047] In some improved embodiments, a custom jump protocol may be registered through a batch script, which may specifically include the following steps:

[0048] Execute the file of the custom jump protocol through the REGEDIT command to write the relevant information of the custom jump protocol into the user-side operating system registry;

[0049] After successful execution, a prompt message indicating successful execution is output;

[0050] According to the prompt information of successful execution, a JavaScript code is run through the mshta command, a prompt box pops up to prompt the user that the registration is successful, and the current window is closed. The JavaScript code uses the ActiveXObject object to create a Shell object of a Windows Script Host to pop up the prompt box.

[0051] It should be noted that REGEDIT is the registry editor in the Windows operating system. mshta is the host of HTML applications in the Windows operating system, and can run HTML files through command lines or script files. JavaScript is a scripting language used to achieve interactive and dynamic effects on web pages. ActiveXObject is a JavaScript object that can be used to create ActiveX objects in the first browser. Windows Script Host is a script execution environment in the Windows operating system that can execute scripting languages ​​such as VBScript and JScript. The Shell object is used to perform file and directory operations in the Windows operating system, such as opening files, creating directories, etc.

[0052] In some improved embodiments, executing the custom jump protocol through a batch script may include the following steps:

[0053] Get the input parameters, including the URL;

[0054] Replace the custom redirect protocol in the passed parameter with empty to get the actual URL to be executed;

[0055] Open the second browser using an open command and open the URL in full screen mode;

[0056] Use the exit command to exit the script execution.

[0057] It should be noted that, in this embodiment, according to the transmitted URL, the second browser is opened and the page corresponding to the URL is displayed in full screen mode, so that the web page jump from the first browser to the second browser can be realized. Wherein, URL is a uniform resource locator.

[0058] In some preferred embodiments, after detecting the completion confirmation information of the user terminal completing the installation of the custom jump protocol registration tool, the method may further include: when the completion confirmation information is not detected, prompting the user terminal to download and install the custom jump protocol registration tool.

[0059] It should be noted that, in this embodiment, when the completion confirmation information is not detected, the user terminal is prompted to download and install a custom jump protocol registration tool, which can guide the user to jump to a web page, thereby improving the user experience.

[0060] In some preferred embodiments, the determination of whether the user-side operating system supports a custom jump protocol may include the following steps: creating a hidden iframe element, the style of which is not displayed on the page of the web page; adding the iframe element to the page of the web page, and setting the address of the iframe element to a set protocol address to indicate that a blank page is loaded; when the address of the iframe element is successfully set to the set protocol address, it is determined that the user-side operating system supports the custom jump protocol, and when the address of the iframe element is failed to be set to the set protocol address, it is determined that the user-side operating system does not support the custom jump protocol. Further, the style of the iframe element is set to display:none, or the style of the iframe element is set to visibility:hidden to hide the style of the iframe element. Further, the set protocol address is about:blank.

[0061] It should be noted that, in this embodiment, a hidden iframe element is created to detect whether the current user-side operating system supports the custom jump protocol, that is, to detect whether the current user-side operating system supports the current web page to jump from the first browser to the second browser. In addition, by creating a hidden iframe element, functions such as embedding advertisements in a page and providing an independent browsing context can be realized without affecting the layout of the web page.

[0062] It should also be noted that display:none can completely delete the iframe element, including the space occupied by the iframe element, while visibility:hidden can make the iframe element retain its space on the page but be invisible. By setting the style of the iframe element to display:none or visibility:hidden, it can be used to control the display and hiding of the iframe element on the page. For example, when the iframe content needs to be dynamically loaded, it can be hidden first and then displayed when needed. In addition, when necessary, unnecessary iframe elements can also be hidden to improve page performance and loading speed.

[0063] It should also be noted that setting the address of the iframe element to the set protocol address can realize web page jump when the user clicks a link or button on the page, but if the user's operating system does not support the custom jump protocol, an error or exception will occur. In this embodiment, the set protocol address is set to about:blank, which means loading a blank page. If the loading of about:blank is successful, it can be determined that the user-side operating system supports the custom jump protocol, otherwise it is determined that the user-side operating system does not support the custom jump protocol. Therefore, setting the set protocol address to about:blank can determine whether the user-side operating system supports the custom jump protocol when the user clicks a link or button on the page, and avoid errors or exceptions when it is not supported, for example, a non-support prompt is given.

[0064] It should be noted that the iframe element is a tool for embedding another web page in a web page, and Display:none is a CSS style used to hide an element and remove its space occupation. Visibility:hidden is a CSS style used to hide an element but retain its space occupation. Among them, CSS (Cascading Style Sheets) is a style sheet language used to control the appearance and layout of web pages. CSS styles control elements in HTML or XML documents by defining a series of styles, including fonts, colors, backgrounds, borders, layouts, etc. CSS styles consist of selectors and attributes, where selectors are used to select elements to which styles are to be applied, and attributes are used to define the styles to be applied.

[0065] In some embodiments, after determining that the user-side operating system does not support the custom jump protocol, it includes: generating a prompt pop-up box to prompt the user-side operating system that the user-side operating system does not support the custom jump protocol; controlling the display of the prompt pop-up box to prompt the user of the user-side.

[0066] It should be noted that, in this embodiment, by generating a prompt pop-up box to prompt that the user-side operating system does not support the custom jump protocol, the user of the user side can be prompted, thereby improving the user experience.

[0067] Specifically in step S3, when the operating system of the user terminal supports the custom jump protocol, the server controls the current webpage to jump from the first browser to the second browser for execution.

[0068] It should be noted that when the user-side operating system supports the custom jump protocol, the server controls the current webpage to jump from the first browser to the second browser, thereby improving the user experience and reducing the server overhead. It is understandable that when the user-side operating system supports the custom jump protocol, the server directly controls the current webpage to jump from the first browser to the second browser, thereby saving server overhead.

[0069] Embodiment 2

[0070] See also Figure 1-4 This embodiment provides a web page jump device compatible with different browsers, including:

[0071] A web page jump request receiving module, used to receive a web page jump request initiated by a user terminal, wherein the web page jump request is a request for a current web page to jump from a first browser to a second browser for execution, and the first browser executes the current web page before the web page jump request is initiated;

[0072] A custom jump protocol support judgment module is used to obtain the user-side operating system information to determine whether the user-side operating system supports the custom jump protocol, wherein the custom jump protocol is for the current web page to jump from the first browser to the second browser;

[0073] The current web page jump control module is used to control the current web page to jump from the first browser to the second browser when the user-side operating system supports a custom jump protocol.

[0074] It should be noted that, in the present embodiment, a web page jump request initiated by a user terminal is received, wherein the web page jump request is a request for the current web page to jump from the first browser to the second browser for execution, and the first browser runs the current web page before the web page jump request is initiated, and the user terminal operating system information is obtained to determine whether the user terminal operating system supports a custom jump protocol, wherein the custom jump protocol is for the current web page to jump from the first browser to the second browser. When the user terminal operating system supports the custom jump protocol, the current web page is controlled to jump from the first browser to the second browser for execution, thereby improving the user experience and reducing the server overhead.

[0075] Embodiment 3

[0076] See also Figure 1-4 This embodiment provides a web page jump system compatible with different browsers, and the web page jump system compatible with different browsers includes:

[0077] A server, comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the web page jump method compatible with different browsers as described in any of the above embodiments when executing the computer program;

[0078] The user end is used to initiate a web page jump request to the server, wherein the web page jump request is to request the current web page to jump from the first browser to the second browser for execution, and the first browser executes the current web page before the web page jump request is initiated.

[0079] In this embodiment, since the web page jump system compatible with different browsers includes a server, when the processor of the server executes a computer program, the web page jump method compatible with different browsers described in any of the above embodiments can be implemented, by receiving a web page jump request initiated by a user terminal, the web page jump request is a request for the current web page to jump from a first browser to a second browser for execution, the first browser runs the current web page before the web page jump request is initiated, and the user terminal operating system information is obtained to determine whether the user terminal operating system supports a custom jump protocol, the custom jump protocol is for the current web page to jump from the first browser to the second browser, and when the user terminal operating system supports the custom jump protocol, the current web page is controlled to jump from the first browser to the second browser for execution, thereby improving user experience and reducing server overhead.

[0080] Embodiment 4

[0081] See also Figure 1-4 This embodiment provides a server, including a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the web page jump method compatible with different browsers described in any of the above embodiments is implemented.

[0082] In this embodiment, since the processor of the server executes the computer program, the web page jump method compatible with different browsers described in any of the above embodiments can be implemented, by receiving a web page jump request initiated by the user end, the web page jump request is a request for the current web page to jump from the first browser to the second browser for execution, the first browser runs the current web page before the web page jump request is initiated, and the user end operating system information is obtained to determine whether the user end operating system supports a custom jump protocol, the custom jump protocol is for the current web page to jump from the first browser to the second browser, and when the user end operating system supports the custom jump protocol, the current web page is controlled to jump from the first browser to the second browser for execution, thereby improving user experience and reducing server overhead.

[0083] It should be noted that the related equipment of the web page jump method compatible with different browsers includes but is not limited to servers, web page jump devices compatible with different browsers and other related equipment.

[0084] It should be pointed out that the above embodiments are only preferred specific implementation modes of the present invention, and the protection scope of the present invention is not limited thereto. Any changes or substitutions that can be easily thought of by any technician familiar with the technical field within the technical scope disclosed by the present invention should be covered within the protection scope of the present invention. The protection scope of the present invention should be based on the protection scope of the claims.

Claims

1. A web page jump method compatible with different browsers, wherein the web page jump method compatible with different browsers is run on a server, and is characterized in that: The web page jump method compatible with different browsers comprises the following steps: S1. Receive a web page jump request initiated by a user terminal, wherein the web page jump request is a request for a current web page to jump from a first browser to a second browser for execution, and the first browser executes the current web page before the web page jump request is initiated; S2, obtaining the user-side operating system information to determine whether the user-side operating system supports a custom jump protocol, where the custom jump protocol is for jumping the current web page from the first browser to the second browser; S3. When the user-side operating system supports a custom jump protocol, control the current webpage to jump from the first browser to the second browser for execution.

2. The web page jump method compatible with different browsers as claimed in claim 1, characterized in that: After obtaining the user-side operating system information to determine whether the user-side operating system supports the custom jump protocol, the method further includes: When the user's operating system does not support the custom jump protocol, the user is prompted to download and install the custom jump protocol registration tool; The completion confirmation information of the installation of the custom jump protocol registration tool by the user end is detected, and when the completion confirmation information is detected, the current webpage is controlled to jump from the first browser to the second browser for execution.

3. The web page jump method compatible with different browsers as claimed in claim 2, characterized in that: After the detection of the completion confirmation information of the user end for the installation of the custom jump protocol registration tool, the method further includes: When the completion confirmation information is not detected, the user terminal is prompted to download and install a custom jump protocol registration tool.

4. The web page jump method compatible with different browsers according to any one of claims 1 to 3, characterized in that: The determining whether the user-side operating system supports the custom jump protocol includes: Creating a hidden iframe element, the style of the iframe element is not displayed on the web page; Add the iframe element to the page of the webpage, and set the address of the iframe element to the set protocol address to indicate loading a blank page; When the address of the iframe element is successfully set to the set protocol address, it is determined that the user-side operating system supports the custom jump protocol. When the address of the iframe element is failed to be set to the set protocol address, it is determined that the user-side operating system does not support the custom jump protocol.

5. The web page jump method compatible with different browsers as claimed in claim 4, characterized in that: After determining that the user-side operating system does not support the custom jump protocol, the following steps are included: Generate a prompt pop-up box indicating that the user-side operating system does not support the custom jump protocol; Control the display of the prompt pop-up box to prompt the user at the user end.

6. The web page jump method compatible with different browsers as claimed in claim 4, characterized in that: The set protocol address is about:blank.

7. The web page jump method compatible with different browsers as claimed in claim 4, characterized in that: The style of the iframe element is set to display:none, or the style of the iframe element is set to visibility:hidden to hide the style of the iframe element.

8. The web page jump method compatible with different browsers as claimed in claim 1, characterized in that: The first browser is IE browser, and the second browser is Chrome browser.

9. A web page jump device compatible with different browsers, characterized in that: include: A web page jump request receiving module, used to receive a web page jump request initiated by a user terminal, wherein the web page jump request is a request for a current web page to jump from a first browser to a second browser for execution, and the first browser executes the current web page before the web page jump request is initiated; A custom jump protocol support judgment module is used to obtain the user-side operating system information to determine whether the user-side operating system supports the custom jump protocol, wherein the custom jump protocol is for the current web page to jump from the first browser to the second browser; The current web page jump control module is used to control the current web page to jump from the first browser to the second browser when the user-side operating system supports a custom jump protocol.

10. A server comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the web page jump method compatible with different browsers as claimed in any one of claims 1 to 8 when executing the computer program.

Images