Web page access method and related equipment based on dynamic access path

By using dynamic access path URLs and encryption algorithms, the vulnerability of webpage access paths to attacks is solved, achieving secure and reliable access path transmission and simplifying protection measures.

CN109977330BActive Publication Date: 2024-11-05PING AN TECH (SHENZHEN) CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN201910186558.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2019-03-12
Publication Date
2024-11-05
Estimated Expiration
2039-03-12

AI Technical Summary

Technical Problem

Webpage access paths are easily obtained by hackers, leading to frequent attacks. Existing protection measures are inefficient and require urgent code modifications.

Method used

By using dynamic access path URLs, combined with the front-end H5 APP and the back-end Spring MVC framework, dynamic values ​​are processed through encryption and decryption algorithms to generate and parse dynamic access paths, thus eliminating the risk of path attacks.

Benefits of technology

It effectively prevents attacks on access paths and data leakage risks. Attacks can be dealt with simply by updating the configuration file, without modifying the control logic, thus simplifying the protection process.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN109977330B_ABST
    Figure CN109977330B_ABST
Patent Text Reader

Abstract

The present invention relates to the field of information security technology, and in particular to a web page access method based on a dynamic access path and related equipment. The method comprises: a front-end H5 APP initiates a web page access request to a back-end server, and the web page access request contains a dynamic access path URL; after the back-end server receives the web page access request, it calls a preset technical framework Spring MVC, reads the dynamic access path URL, and obtains mapping data; the back-end server feeds back the mapping data to the front-end H5 APP. The present invention designs the access path requested by the front-end H5 APP as a dynamic access path URL, combines the front-end H5 APP with the Spring MVC of the back-end server, obtains mapping data according to the dynamic access path URL through the annotation of Spring MVC, and in the interactive process, even if attacked by someone, the path is obtained without risk, eliminating the hidden danger of attack.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of information security technology, and in particular to a web page access method based on a dynamic access path and related equipment. Background Art

[0002] With the development of Internet technology, people are becoming more and more dependent on the Internet. Various network services are gradually penetrating into people's study, life and work, and the security of network information is gradually receiving attention.

[0003] When users access a page, the access path of their page request is easily obtained by hackers or people who want to steal data, which makes it easy for attacks to occur. When an attack occurs, the server needs to write a lot of code to control the anti-attack logic, but there are often omissions, and after discovering an attack, there is no other more effective way except to modify the control logic and issue an emergency version for processing. Summary of the invention

[0004] In view of this, it is necessary to provide a web page access method and related equipment based on a dynamic access path to address the problem that the access path is easily obtained and the web page is easily attacked when accessing the web page.

[0005] A web page access method based on a dynamic access path, comprising:

[0006] The front-end hypertext markup language application software H5 APP initiates a web page access request to the back-end server, wherein the web page access request includes a dynamic access path URL;

[0007] After receiving the web page access request, the back-end server calls the preset technical framework SpringMVC, reads the dynamic access path URL, and obtains the mapping data through the dynamic access path URL;

[0008] The back-end server feeds back the mapping data to the front-end H5 APP.

[0009] In a possible design, the front-end hypertext markup language H5 APP initiates a web page access request to the back-end server, including:

[0010] The front-end H5 APP obtains the dynamic parameters in the URL, reads the dynamic values ​​corresponding to the dynamic parameters from the front-end parameter configuration file, replaces the dynamic parameters in the URL with the dynamic values, and generates a dynamic access path URL. The front-end parameter configuration file is preset with dynamic parameters and corresponding dynamic values;

[0011] The front-end H5 APP initiates a web page access request including the dynamic access path URL to the back-end server.

[0012] In a possible design, replacing the dynamic parameters in the URL with dynamic values ​​to generate a dynamic access path URL includes:

[0013] The front-end H5 APP monitors whether the webpage is normal through a preset monitoring script. If an abnormality occurs, the encryption type corresponding to the dynamic value and the characteristic parameter corresponding to the encryption type are read from the front-end parameter configuration file, and the corresponding preset encryption algorithm is called according to the encryption type to encrypt the dynamic value to obtain a ciphertext;

[0014] The ciphertext and the characteristic parameter are concatenated to obtain a new dynamic value, and the dynamic parameter in the URL is replaced with the new dynamic value to generate a dynamic access path URL.

[0015] In a possible design, after receiving the web page access request, the backend server calls the preset technical framework Spring MVC, reads the dynamic access path URL, and obtains mapping data through the dynamic access path URL, including:

[0016] Read the dynamic access path URL through the Spring MVC distributor DispatcherServlet, and obtain a dynamic value from the dynamic access path URL;

[0017] Read the dynamic parameter corresponding to the dynamic value from the preset backend parameter configuration file, replace the dynamic value in the dynamic access path URL with the dynamic parameter, and generate a mapping URL;

[0018] The mapping data corresponding to the mapping URL is obtained through the @RequestMapping annotation of the Spring MVC.

[0019] In a possible design, after receiving the web page access request, the backend server calls the preset technical framework Spring MVC, reads the dynamic access path URL, obtains the mapping data through the dynamic access path URL, and further includes:

[0020] Determine whether the acquired dynamic value contains characteristic parameters. If so, read the encryption type corresponding to the characteristic parameters from the backend parameter configuration file, call the corresponding preset decryption algorithm according to the encryption type, decrypt the dynamic value, and obtain the decrypted dynamic value.

[0021] In a possible design, the backend server feeds back the mapping data to the frontend H5APP, including:

[0022] Determine whether the dynamic access path URL contains characteristic parameters, and if so, read the encryption type corresponding to the characteristic parameters from the backend parameter configuration file, call the corresponding preset encryption algorithm according to the encryption type, encrypt the mapping data, and obtain ciphertext;

[0023] The ciphertext and the characteristic parameters are concatenated to obtain new mapping data, and the mapping data is fed back to the front-end H5 APP.

[0024] A possible design also includes:

[0025] The front-end H5 APP receives the dynamic parameters and corresponding dynamic values ​​input by the user through a preset front-end configuration interface, and updates the front-end parameter configuration file;

[0026] The backend server receives the dynamic value and the corresponding dynamic parameter input by the user through a preset backend configuration interface, and updates the backend parameter configuration file.

[0027] A web page access device based on a dynamic access path, comprising:

[0028] A request initiation module is used for the front-end hypertext markup language application software H5 APP to initiate a web page access request to the back-end server, wherein the web page access request includes a dynamic access path URL;

[0029] A mapping data acquisition module is used for, after the back-end server receives the webpage access request, to call the preset technical framework Spring MVC, read the dynamic access path URL, and obtain the mapping data through the dynamic access path URL;

[0030] A feedback module is used for the back-end server to feed back the mapping data to the front-end H5 APP.

[0031] A computer device includes a memory and a processor, wherein the memory stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the processor executes the steps of the web page access method based on the dynamic access path.

[0032] A storage medium storing computer-readable instructions, when the computer-readable instructions are executed by one or more processors, enables the one or more processors to execute the steps of the above-mentioned web page access method based on dynamic access path.

[0033] The web page access method, device, computer equipment and storage medium based on dynamic access path include a front-end hypertext markup language application software H5 APP initiating a web page access request to a back-end server, wherein the web page access request includes a dynamic access path URL; after receiving the web page access request, the back-end server calls the preset technical framework Spring MVC, reads the dynamic access path URL, and obtains mapping data through the dynamic access path URL; the back-end server feeds back the mapping data to the front-end H5 APP. The present invention designs the access path requested by the front-end H5 APP as a dynamic access path URL, combines the front-end H5 APP with the Spring MVC of the back-end server, obtains mapping data according to the dynamic access path URL through the annotation of SpringMVC, and in the interactive process, even if attacked by someone, the path is obtained without risk, eliminating the hidden danger of attack. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Various other advantages and benefits will become apparent to those of ordinary skill in the art by reading the following detailed description of the preferred embodiment.The drawings are only for the purpose of illustrating the preferred embodiments and are not to be construed as limiting the invention.

[0035] Figure 1 A flowchart of a web page access method based on a dynamic access path in one embodiment of the present invention;

[0036] Figure 2 is a flow chart of step S1 in one embodiment;

[0037] Figure 3 is a flow chart of step S101 in one embodiment;

[0038] Figure 4 is a flow chart of step S2 in one embodiment;

[0039] Figure 5 is a flow chart of step S3 in one embodiment;

[0040] Figure 6 The structure diagram of a web page access device based on a dynamic access path in one embodiment of the present invention. DETAILED DESCRIPTION

[0041] 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.

[0042] Those skilled in the art will appreciate that, unless otherwise stated, the singular forms "a", "an", "said" and "the" used herein may also include plural forms. It should be further understood that the term "comprising" used in the specification of the present invention refers to the presence of the features, integers, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or groups thereof.

[0043] Figure 1 FIG. 1 is a flow chart of a web page access method based on a dynamic access path in one embodiment of the present invention. Figure 1 As shown, a web page access method based on a dynamic access path includes the following steps:

[0044] Step S1, initiating a web page access request: the front-end hypertext markup language application software H5 APP initiates a web page access request to the back-end server, and the web page access request includes a dynamic access path URL.

[0045] The H5 in this step is the fifth revised version of Hypertext Markup Language, called "HTML5", or "H5" for short. Hypertext Markup Language is an application under the Standard Generalized Markup Language, and is also a specification or standard. It uses tag symbols to mark the various parts of the web page to be displayed. The web page file itself is a text file. By adding tags to the text file, you can tell the browser how to display the content, such as: how to process text, how to arrange the screen, how to display pictures, etc. The browser reads the web page file in sequence, and then interprets and displays the marked content according to the tags. Since Hypertext Markup Language documents are simple to make, highly scalable, powerful, and support the embedding of files in different data formats, this step uses H5 to develop interactive pages on the front end, interact with users through the front-end H5 APP, and display and interact with users.

[0046] When the front-end H5 APP interacts with the user, it receives the interaction request initiated by the user, obtains the original URL, generates a dynamic access path URL, and then initiates a web page access request to the back-end server.

[0047] In one embodiment, step S1, as Figure 2 As shown, including:

[0048] Step S101, generate a dynamic access path URL: the front-end H5 APP obtains the dynamic parameters in the URL, reads the dynamic values ​​corresponding to the dynamic parameters from the front-end parameter configuration file, replaces the dynamic parameters in the URL with the dynamic values, and generates a dynamic access path URL. The front-end parameter configuration file is preset with dynamic parameters and corresponding dynamic values.

[0049] The front-end H5 APP presets a front-end parameter configuration file. The front-end parameter configuration file can use a json configuration file. The front-end parameter configuration file is set with dynamic parameters and corresponding dynamic values, for example:

[0050] / pw / iloan=iloan.url.1111;

[0051] / iloan / entern=iloan.url.2222;

[0052] In this step, the front-end H5 APP modifies the request method before initiating the request, and changes the original URL to a dynamic configuration method, that is, replacing the original dynamic parameters with dynamic values, resulting in a new dynamic access path URL. For example:

[0053] The original request method is:

[0054] $.ajax({

[0055] url:realPath+' / pw / iloan / queryIloanState.do',

[0056] type:"POST",

[0057] The dynamic parameter is / pw / iloan. The front-end H5 APP reads the dynamic value of the dynamic parameter from the front-end parameter configuration file, which is iloan.url.1111. After replacing the dynamic parameter with the dynamic value, the new dynamic access path URL generated is:

[0058] $.ajax({

[0059] url:realPath+'{iloan.url.1111} / queryIloanState.do',

[0060] type:"POST",

[0061] Step S102, initiating a request: the front-end H5 APP initiates a web page access request containing a dynamic access path URL to the back-end server.

[0062] In the request initiated by the front-end H5 APP to the back-end server in this step, the dynamic access path URL contained is the new dynamic access path URL generated in step S101. The following methods can be used to initiate the request:

[0063] $.ajax({

[0064] url:url,

[0065] type:"POST"

[0066] After the dynamic parameters are replaced with dynamic values ​​in this embodiment, even if the access path in the request is stolen by an attack during the process of initiating a web page access request, what is displayed is a dynamic value such as iloan.url.1111, which is not the actual access path. Therefore, it will not cause any risks and eliminates the hidden dangers of data leakage after the access path is attacked.

[0067] In one embodiment, in step S101, the dynamic parameters in the URL are replaced with dynamic values ​​to generate a dynamic access path URL, such as Figure 3 As shown, including:

[0068] Step S10101, monitoring and encryption: The front-end H5 APP monitors whether the web page is normal through a preset monitoring script. If an abnormality occurs, the encryption type corresponding to the dynamic value and the characteristic parameters corresponding to the encryption type are read from the front-end parameter configuration file, and the corresponding preset encryption algorithm is called according to the encryption type to encrypt the dynamic value to obtain the ciphertext.

[0069] When monitoring a web page, the front-end H5 APP can use a wget or curl monitoring script for monitoring. During monitoring, the return value of the wget or curl command is used to determine whether the monitored web page is normal. If the return value of the wget command is non-0, or the return value of the curl command is non-200, it is determined that an abnormal situation has occurred in the monitored web page. At this time, in order to further ensure the security and reliability of the access path, the dynamic value in the URL is encrypted. The encryption type and encryption algorithm used in the encryption process are preset in the front-end H5 APP. When preset, the same encryption type can be set for each dynamic value, and the corresponding encryption algorithm is preset. An encryption type can also be selected for different dynamic values, and each encryption type is configured with corresponding characteristic parameters for distinguishing encryption types. The encryption types of this step include symmetric encryption types, asymmetric encryption types, message digest encryption types, etc., and the corresponding encryption algorithms include symmetric encryption algorithms, such as DES algorithms, asymmetric encryption algorithms, such as RSA algorithms, and message digest algorithms, such as MD5 algorithms.

[0070] Step S10102, concatenation: concatenate the ciphertext and the characteristic parameters to obtain a new dynamic value, replace the dynamic parameters in the URL with the new dynamic value, and generate a dynamic access path URL.

[0071] Since the dynamic value is encrypted and there may be multiple encryption types and encryption algorithms, in order to determine the encryption type each time, this step generates a new dynamic value together with the characteristic parameters corresponding to the encryption type and the ciphertext. After initiating an access request, the back-end server can be informed of the encryption type used by the ciphertext, so that the back-end server can select the corresponding decryption algorithm to decrypt the ciphertext.

[0072] When concatenating, place the ciphertext before the characteristic parameter and separate them with commas to form a new dynamic value. For example, dynamic value = ciphertext, characteristic parameter. The new dynamic access path URL generated is:

[0073] $.ajax({

[0074] url:realPath+'{ciphertext, characteristic parameters} / queryIloanState.do',

[0075] type:"POST",

[0076] This embodiment also monitors whether the web page URL is abnormal. When an abnormal situation occurs, the access path is encrypted and spliced ​​to further ensure the security of the access request process and prevent data leakage after the access path is attacked.

[0077] Step S2, obtaining mapping data: after receiving the web page access request, the backend server calls the preset technical framework Spring MVC, reads the dynamic access path URL, and obtains the mapping data through the dynamic access path URL.

[0078] The MVC in this step is Model View Controller, which is the abbreviation of model, view, and controller. MVC organizes code in a way that separates business logic, data, and interface display, and gathers business logic into one component. While improving and personalizing the interface and user interaction, there is no need to rewrite the business logic. MVC is widely used to map traditional input, processing, and output functions into a logical graphical user interface structure. Spring MVC is a framework of MVC. Spring MVC has excellent scalability and flexibility, supports annotation configuration, and is very suitable for reading dynamic access path URLs and obtaining mapping data in this step.

[0079] In one embodiment, step S2, such as Figure 4 As shown, including:

[0080] Step S201, obtaining a dynamic value: reading the dynamic access path URL through the Spring MVC distributor DispatcherServlet, and obtaining a dynamic value from the dynamic access path URL.

[0081] The backend server uses Spring MVC to respond to the request initiated by the frontend H5 APP. Its complete dynamic access path URL is matched and trimmed according to the URL format preset by DispatcherServlet. The remaining part of the URL is the dynamic value in this step.

[0082] Before using DispatcherServlet to obtain dynamic values, the DispatcherServlet configuration in Spring MVC is rewritten to change the configuration to a wildcard configuration to meet the dynamic configuration requirements. For example, the original DispatcherServlet configuration supports:

[0083] @RequestMapping(" / iloan / queryIloanState.do")

[0084] Modified configuration supports:

[0085] @RequestMapping("${iloan.url.*} / queryIloanState.do")

[0086] When modifying, the preset configuration modification interface is used to obtain the modification data entered by the user, and the configuration information is updated to match the dynamic access path URL sent by the front-end H5 APP.

[0087] Step S202, generating a mapping URL: reading dynamic parameters corresponding to dynamic values ​​from a preset backend parameter configuration file, replacing the dynamic values ​​in the dynamic access path URL with the dynamic parameters, and generating a mapping URL.

[0088] The backend server has a preset backend parameter configuration file. The backend parameter configuration file can use the iloan.properties configuration file. The backend parameter configuration file is set with dynamic values ​​and corresponding dynamic parameters, for example:

[0089] iloan.url.1111 = / pw / iloan;

[0090] iloan.url.2222= / iloan / entern;

[0091] After the backend server obtains the dynamic value iloan.url.1111 from step S201, it reads the corresponding dynamic parameter / pw / iloan from the backend parameter configuration file, and replaces the dynamic value with the dynamic parameter. The generated new mapping URL is:

[0092] @RequestMapping("${ / pw / iloan} / queryIloanState.do");

[0093] Step S203, obtaining mapping data: obtaining mapping data corresponding to the mapping URL through the @RequestMapping annotation of Spring MVC.

[0094] The @RequestMapping annotation in this step is used to process request address mapping. It can be annotated on a class or a method in a class. When annotated on a class, it indicates the unified identifier of the controller, usually the identifier of a module. When annotated on a method, it indicates that the request is processed by the corresponding method.

[0095] The backend server maps through the @RequestMapping annotation, performs specific processing, and returns the corresponding mapping data.

[0096] This embodiment uses Spring MVC to respond to the request initiated by the front-end H5 APP to achieve the response to the dynamic access path URL, configures the dynamic value in the dynamic access path URL through the back-end parameter configuration file, and obtains the mapping data through the @RequestMapping annotation.

[0097] In one embodiment, step S201 also includes: determining whether the acquired dynamic value contains characteristic parameters; if so, reading the encryption type corresponding to the characteristic parameters from the backend parameter configuration file, calling the corresponding preset decryption algorithm according to the encryption type, decrypting the dynamic value, and obtaining the decrypted dynamic value.

[0098] When judging whether the dynamic value contains characteristic parameters, the judgment is made according to the splicing rule of step S10102. If the splicing rule adopted by the dynamic value in the request sent by the front-end H5 APP is dynamic value = ciphertext, characteristic parameter type, then when the dynamic value contains a comma, it is judged to contain characteristic parameters, and the ciphertext is before the comma, and the characteristic parameter is after the comma.

[0099] The backend parameter configuration file has preset characteristic parameters and corresponding encryption types, and each encryption type has a decryption algorithm. The backend server obtains the encryption type corresponding to the characteristic parameter from the backend parameter configuration file, and decrypts the ciphertext before the comma using the corresponding decryption algorithm to obtain the real dynamic value.

[0100] This embodiment is a response to the encrypted dynamic value after an abnormal situation occurs on the web page in step S1. The real dynamic value is obtained through a decryption algorithm corresponding to the encryption type. Under the premise of eliminating attack risks and ensuring the security of access requests, normal access is guaranteed.

[0101] Step S3, feedback data: the backend server feeds back the mapping data to the frontend H5 APP, such as Figure 5 As shown, specifically including:

[0102] Step S301, encrypt the mapping data: determine whether the dynamic access path URL contains characteristic parameters. If so, read the encryption type corresponding to the characteristic parameters from the backend parameter configuration file, call the corresponding preset encryption algorithm according to the encryption type, encrypt the mapping data, and obtain the ciphertext.

[0103] The characteristic parameter is an identifier of whether the dynamic value in the dynamic access path URL is encrypted. If the dynamic value is encrypted, it contains the characteristic parameter. When the dynamic value in the request sent by the front-end H5 APP is encrypted, it is considered that there is an abnormality in the webpage. In order to achieve safe data transmission, the back-end server should also encrypt the mapping data before feeding back the mapping data, and preferably use the same encryption type. The encryption type is determined by the characteristic parameters and corresponding encryption types preset in the back-end parameter configuration file. The back-end server also presets the encryption algorithm corresponding to the encryption type, and encrypts the mapping data through the encryption algorithm to finally obtain the ciphertext.

[0104] Step S302, splicing and feedback: splicing the ciphertext and feature parameters to obtain new mapping data, and feeding back the mapping data to the front-end H5 APP.

[0105] When splicing, the same splicing rules as the front-end H5 APP can be used, such as placing the ciphertext before the characteristic parameters and separating them with commas to form new mapping data: mapping data = ciphertext', characteristic parameters. This step uses encryption processing before transmission to ensure the security and stability of the data transmission process.

[0106] In one embodiment, it also includes: the front-end H5 APP receives the dynamic parameters and corresponding dynamic values ​​input by the user through a preset front-end configuration interface, and updates the front-end parameter configuration file; the back-end server receives the dynamic values ​​and corresponding dynamic parameters input by the user through a preset back-end configuration interface, and updates the back-end parameter configuration file.

[0107] When the front-end H5 APP detects an abnormality on a web page through a preset monitoring script, the front-end H5 APP can also use a preset reminder method to remind the user of the page abnormality and suggest modifying the configuration file. The reminder method may include automatic dialing voice reminders through a preset mobile phone number, automatic email reminders through a preset mailbox, and the like. In order for the user to modify the configuration file conveniently, this embodiment can modify the front-end parameter configuration file and the back-end parameter configuration file respectively through the front-end configuration interface and the back-end configuration interface. Provide users with operations such as replacement, modification, or deletion of parameter configuration files.

[0108] The above method is easy to cause inconsistency of dynamic parameters and dynamic values ​​due to independent configuration in different scenarios, resulting in confusion. Therefore, when modifying the configuration, you can also use the following methods:

[0109] A file monitor is preset on the front-end server to monitor the front-end parameter configuration file. When the front-end parameter configuration file is updated, the file monitor is triggered to read the front-end parameter configuration file and send the configuration data in the front-end parameter configuration file to the back-end server. The back-end server updates the configuration data to the back-end parameter configuration file. After the update is completed, the back-end server is restarted to complete the unified configuration of the front and back ends.

[0110] The present invention provides an entry for users to modify configuration files. Even if the access webpage and access path are maliciously attacked, users do not need to modify the control logic and issue an emergency version to solve the problem. They only need to modify the configuration files through the front-end and back-end configuration interfaces, which is simple and convenient to maintain.

[0111] The web page access method based on the dynamic access path of the embodiment of the present invention adopts a dynamic access path URL access request combined with a configuration file, and adopts a splicing method to prevent the entire path of the request from being obtained and attacked. In the event of an abnormality on the web page, the secure transmission of data is guaranteed by encryption. Even if the web page is attacked, it only needs to modify the configuration file through the configuration interface, without modifying the control logic and issuing an emergency version, to effectively solve the attack problem.

[0112] In one embodiment, a web page access device based on a dynamic access path is proposed, such as Figure 6 As shown, it includes the following modules:

[0113] A request initiation module is used for the front-end hypertext markup language application software H5 APP to initiate a web page access request to the back-end server, wherein the web page access request includes a dynamic access path URL;

[0114] A mapping data acquisition module is used for, after the back-end server receives the webpage access request, to call the preset technical framework Spring MVC, read the dynamic access path URL, and obtain the mapping data through the dynamic access path URL;

[0115] A feedback module is used for the back-end server to feed back the mapping data to the front-end H5 APP.

[0116] In one embodiment, a computer device is proposed, including a memory and a processor, wherein the memory stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the processor implements the steps of the web page access method based on dynamic access path in the above-mentioned embodiments when executing the computer-readable instructions.

[0117] In one embodiment, a storage medium storing computer-readable instructions is provided, and when the computer-readable instructions are executed by one or more processors, the one or more processors execute the steps in the webpage access method based on dynamic access path in the above embodiments. The storage medium may be a non-volatile storage medium.

[0118] A person of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable storage medium, and the storage medium may include: a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, etc.

[0119] The technical features of the above-described embodiments may be arbitrarily combined. To make the description concise, not all possible combinations of the technical features in the above-described embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0120] The above-mentioned embodiments only express some exemplary embodiments of the present invention, and the description thereof is relatively specific and detailed, but it cannot be understood as limiting the scope of the patent of the present invention. It should be pointed out that, for ordinary technicians in this field, several variations and improvements can be made without departing from the concept of the present invention, which all belong to the protection scope of the present invention. Therefore, the protection scope of the patent of the present invention shall be based on the attached claims.

Claims

1. A web page access method based on dynamic access path, characterized in that: include: The front-end hypertext markup language application software H5 APP initiates a web page access request to the back-end server, wherein the web page access request includes a dynamic access path URL; After receiving the webpage access request, the backend server calls the preset technical framework Spring MVC, reads the dynamic access path URL, and obtains the mapping data through the dynamic access path URL; The backend server feeds back the mapping data to the frontend H5 APP; The front-end hypertext markup language H5 APP initiates a web page access request to the back-end server, including: The front-end H5 APP obtains the dynamic parameters in the URL, reads the dynamic values ​​corresponding to the dynamic parameters from the front-end parameter configuration file, replaces the dynamic parameters in the URL with the dynamic values, and generates a dynamic access path URL. The front-end parameter configuration file is preset with dynamic parameters and corresponding dynamic values; The front-end H5 APP initiates a web page access request including the dynamic access path URL to the back-end server; The step of replacing the dynamic parameters in the URL with dynamic values ​​to generate a dynamic access path URL includes: The front-end H5 APP monitors whether the webpage is normal through a preset monitoring script. If an abnormality occurs, the encryption type corresponding to the dynamic value and the characteristic parameter corresponding to the encryption type are read from the front-end parameter configuration file, and the corresponding preset encryption algorithm is called according to the encryption type to encrypt the dynamic value to obtain a ciphertext; The ciphertext and the characteristic parameter are concatenated to obtain a new dynamic value, and the dynamic parameter in the URL is replaced with the new dynamic value to generate a dynamic access path URL; After receiving the web page access request, the backend server calls the preset technical framework Spring MVC, reads the dynamic access path URL, and obtains mapping data through the dynamic access path URL, including: Read the dynamic access path URL through the Spring MVC distributor DispatcherServlet, and obtain a dynamic value from the dynamic access path URL; Read the dynamic parameter corresponding to the dynamic value from the preset backend parameter configuration file, replace the dynamic value in the dynamic access path URL with the dynamic parameter, and generate a mapping URL; Obtain the mapping data corresponding to the mapping URL through the @RequestMapping annotation of the Spring MVC; After receiving the web page access request, the backend server calls the preset technical framework Spring MVC, reads the dynamic access path URL, and obtains mapping data through the dynamic access path URL, further comprising: Determine whether the acquired dynamic value contains characteristic parameters. If so, read the encryption type corresponding to the characteristic parameters from the backend parameter configuration file, call the corresponding preset decryption algorithm according to the encryption type, decrypt the dynamic value, and obtain the decrypted dynamic value.

2. The web page access method based on dynamic access path according to claim 1, characterized in that: The backend server feeds back the mapping data to the frontend H5 APP, including: Determine whether the dynamic access path URL contains characteristic parameters, and if so, read the encryption type corresponding to the characteristic parameters from the backend parameter configuration file, call the corresponding preset encryption algorithm according to the encryption type, encrypt the mapping data, and obtain ciphertext; The ciphertext and the characteristic parameters are concatenated to obtain new mapping data, and the mapping data is fed back to the front-end H5 APP.

3. The web page access method based on dynamic access path according to claim 1, characterized in that: Also includes: The front-end H5 APP receives the dynamic parameters and corresponding dynamic values ​​input by the user through a preset front-end configuration interface, and updates the front-end parameter configuration file; The backend server receives the dynamic value and the corresponding dynamic parameter input by the user through a preset backend configuration interface, and updates the backend parameter configuration file.

4. A web page access device based on a dynamic access path, characterized in that: include: A request initiation module is used for the front-end hypertext markup language application software H5 APP to initiate a web page access request to the back-end server, wherein the web page access request includes a dynamic access path URL; A mapping data acquisition module is used for, after the back-end server receives the webpage access request, to call the preset technical framework Spring MVC, read the dynamic access path URL, and obtain the mapping data through the dynamic access path URL; A feedback module, used for the back-end server to feed back the mapping data to the front-end H5 APP; The request initiation module is also used for the front-end H5 APP to obtain dynamic parameters in the URL, read the dynamic values ​​corresponding to the dynamic parameters from the front-end parameter configuration file, replace the dynamic parameters in the URL with the dynamic values, and generate a dynamic access path URL. The front-end parameter configuration file is preset with dynamic parameters and corresponding dynamic values; the front-end H5 APP initiates a web page access request containing the dynamic access path URL to the back-end server; The request initiation module is also used for the front-end H5 APP to monitor whether the webpage is normal through a preset monitoring script. If an abnormality occurs, the encryption type corresponding to the dynamic value and the characteristic parameter corresponding to the encryption type are read from the front-end parameter configuration file, and the corresponding preset encryption algorithm is called according to the encryption type to encrypt the dynamic value to obtain a ciphertext; the ciphertext and the characteristic parameter are concatenated to obtain a new dynamic value, and the dynamic parameter in the URL is replaced with the new dynamic value to generate a dynamic access path URL; The mapping data acquisition module is also used to read the dynamic access path URL through the Spring MVC distributor DispatcherServlet, and obtain the dynamic value from the dynamic access path URL; read the dynamic parameter corresponding to the dynamic value from the preset backend parameter configuration file, replace the dynamic value in the dynamic access path URL with the dynamic parameter, and generate a mapping URL; obtain the mapping data corresponding to the mapping URL through the Spring MVC @RequestMapping annotation; The mapping data acquisition module is also used to determine whether the acquired dynamic value contains characteristic parameters. If so, the encryption type corresponding to the characteristic parameters is read from the back-end parameter configuration file, and the corresponding preset decryption algorithm is called according to the encryption type to decrypt the dynamic value to obtain the decrypted dynamic value.

5. A computer device comprising a memory and a processor, wherein the memory stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the processor executes the steps of the web page access method based on dynamic access path as described in any one of claims 1 to 3.

6. A storage medium storing computer-readable instructions, wherein when the computer-readable instructions are executed by one or more processors, the one or more processors execute the steps of the web page access method based on dynamic access path as claimed in any one of claims 1 to 3.