CN112487339B - Response method, device, equipment and storage medium for Web page request - Google Patents

Abstract

The invention discloses a response method of a Web page request, which is applied to a back-end local server and comprises the following steps: receiving a Web page request sent by a front-end remote server; analyzing the Web page request to obtain a target static resource file to be acquired; acquiring a target static resource file from a rear-end local preset directory by utilizing a Spring Boot frame, and constructing a service running environment by utilizing the target static resource file so as to respond to a Web page request; each static resource file in the back-end local preset directory is pulled from the front-end remote server through a JSch frame. By applying the response method of the Web page request, the management and maintenance cost of the back-end developer on the front-end static resource is reduced, and the response efficiency of the Web page request is improved. The invention also discloses a response device, equipment and storage medium for the Web page request, which have corresponding technical effects.

Description

Response method, device, equipment and storage medium for web page request

technical field

The invention relates to the technical field of software development, in particular to a method, device, equipment and computer-readable storage medium for responding to a Web page request.

Background technique

With the development of software engineering theory and the application of modern software development technology, the functions that a single software can provide are becoming more and more complex, and the amount of code is also increasing. In order to develop and maintain software in a systematic, standardized, and quantifiable process-based approach, a clear division of functions is also essential.

Now an ordinary web software often consists of front-end static resources and back-end web services. Front-end static resources are completed by front-end developers, providing page style layout and user interaction functions. Back-end Web services are completed by back-end developers, providing specific business implementation and data persistence capabilities. Some software projects are closely integrated with the front and back ends. In the process of responding to the front-end Web page requests, the back-end server is required to provide corresponding service operating environment support. However, most software developers are only good at the technical direction of their actual application. For example, back-end developers often don't know much about the technical framework and construction methods used by front-end developers, and vice versa. As a result, the management and maintenance costs of front-end static resources for back-end developers are high, and the response efficiency of Web page requests is low.

To sum up, how to effectively solve the problems of high cost of management and maintenance of front-end static resources by back-end developers and low efficiency of Web page request response is an urgent problem for those skilled in the art.

Contents of the invention

The purpose of the present invention is to provide a method for responding to Web page requests, which reduces the management and maintenance costs of front-end static resources for back-end developers, and improves Web page request response efficiency; another purpose of the present invention is to provide a A response device, device, and computer-readable storage medium for a Web page request.

In order to solve the above technical problems, the present invention provides the following technical solutions:

A method for responding to web page requests, applied to the backend local server, including:

Receive the web page request sent by the front-end remote server;

Analyzing the web page request to obtain the target static resource file to be acquired;

Using the Spring Boot framework to obtain the target static resource file from the back-end local preset directory, and using the target static resource file to build a service operating environment to respond to the Web page request;

Wherein, each static resource file in the back-end local preset directory is obtained by pulling from the front-end remote server through the JSch framework.

In a specific implementation of the present invention, after using the Spring Boot framework to obtain the target static resource from the back-end local preset directory, it also includes:

Use the Nginx reverse proxy server to reverse proxy the Spring Boot framework.

In a specific embodiment of the present invention, also include:

Using the JSch framework to update each of the static resource files in the backend local preset directory.

In a specific embodiment of the present invention, using the JSch framework to update each of the static resource files in the back-end local preset directory includes:

Respectively obtain the remote file update time corresponding to each of the static resource files in the front-end remote server, and the local file update time corresponding to each of the static resource files in the back-end local preset directory;

Judging whether there is a remote file update time greater than the corresponding local file update time in each of the remote file update times;

If so, then determine the remote static resource file corresponding to the remote file update time greater than the corresponding local file update time as the target remote static resource file;

Using the JSch framework to pull the target remote static resource file from the front-end remote server to replace the corresponding static resource file in the back-end local preset directory with the target remote static resource file.

In a specific implementation manner of the present invention, after using the target remote static resource file to replace the corresponding static resource file in the back-end local preset directory, it further includes:

Traversing the full path file names corresponding to each of the static resource files in the back-end local preset directory;

Judging whether each of the full-path file names exists in the full-path file name list; wherein, the full-path file name list is generated according to the survival status of each of the static resource files in the back-end local preset directory list of;

If not, delete the static resource files corresponding to the full-path file names that do not exist in the full-path file name list in the back-end local preset directory.

A response device for a web page request, applied to a backend local server, comprising:

The request receiving module is used to receive the Web page request sent by the front-end remote server;

A request parsing module, configured to parse the web page request to obtain the target static resource file to be acquired;

The request response module is used to obtain the target static resource file from the back-end local preset directory by using the Spring Boot framework, and use the target static resource file to build a service operating environment to respond to the Web page request;

Wherein, each static resource file in the back-end local preset directory is obtained by pulling from the front-end remote server through the JSch framework.

In a specific embodiment of the present invention, also include:

The reverse proxy module is used to use the Nginx reverse proxy server to reverse proxy the Spring Boot framework after using the Spring Boot framework to obtain the target static resource from the backend local preset directory.

In a specific embodiment of the present invention, also include:

A file update module, configured to use the JSch framework to update each of the static resource files in the back-end local preset directory.

A device for responding to web page requests, including:

memory for storing computer programs;

The processor is configured to implement the steps of the method for responding to a Web page request as described above when executing the computer program.

A computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the steps of the above method for responding to a Web page request are implemented.

The response method of the Web page request provided by the present invention is applied to the back-end local server, and receives the Web page request sent by the front-end remote server; parses the Web page request to obtain the target static resource file to be obtained; utilizes the Spring Boot framework from Obtain the target static resource files in the back-end local preset directory, and use the target static resource files to build the service operating environment to respond to web page requests; among them, each static resource file in the back-end local preset directory is passed through JSch Frameworks are pulled from the front-end remote server. By pre-deploying the Spring Boot framework and the JSch framework, use the JSch framework to pre-pull each static resource file from the front-end remote server to the back-end local preset directory, and use the Spring Boot framework as a service proxy to obtain it from the back-end local preset directory Target static resource files, thereby reducing the management and maintenance costs of front-end static resources for back-end developers, and improving the efficiency of Web page request response.

Correspondingly, the present invention also provides a Web page request response device, device, and computer-readable storage medium corresponding to the above-mentioned method for responding to a Web page request, which have the above-mentioned technical effects and will not be repeated here.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only These are some embodiments of the present invention. Those skilled in the art can also obtain other drawings based on these drawings without creative work.

Fig. 1 is a kind of implementation flowchart of the response method of Web page request in the embodiment of the present invention;

Fig. 2 is another implementation flowchart of the response method of Web page request in the embodiment of the present invention;

Fig. 3 is a structural block diagram of a response device for a Web page request in an embodiment of the present invention;

Fig. 4 is a structural block diagram of a device responding to a Web page request in an embodiment of the present invention.

Detailed ways

In order to enable those skilled in the art to better understand the solution of the present invention, the present invention will be further described in detail below in conjunction with the accompanying drawings and specific embodiments. Apparently, the described embodiments are only some of the embodiments of the present invention, but not all of them. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present invention.

Embodiment one:

Referring to Fig. 1, Fig. 1 is a kind of implementation flowchart of the response method of Web page request in the embodiment of the present invention, is applied to back-end local server, and this method can comprise the following steps:

S101: Receive a web page request sent by a front-end remote server.

When a user needs to browse a Web page in the front-end remote server, the front-end remote server generates a Web page request according to the browsing instruction input by the user, and sends the Web page request to the back-end local server. The back-end local server receives the web page request sent by the front-end remote server.

S102: Analyzing the web page request to obtain the target static resource file to be obtained.

The web page request includes the target static resource file to be obtained. After receiving the web page request, the backend local server parses the web page request to obtain the target static resource file to be obtained.

The target static resource files to be obtained may include image files, script files, and the like.

S103: Use the Spring Boot framework to obtain the target static resource file from the back-end local preset directory, and use the target static resource file to build a service operating environment to respond to the web page request.

Wherein, each static resource file in the back-end local preset directory is obtained by pulling from the front-end remote server through the JSch framework.

Pre-deploy the Spring Boot framework and JSch framework, and pre-create the back-end local default directory, and use the JSch framework to pre-pull each static resource file from the front-end remote server to the back-end local default directory. After parsing the target static resource file to be obtained, use the Spring Boot framework as a service proxy to obtain the target static resource file from the back-end local preset directory, and use the target static resource file to build the service operating environment to achieve front-end and back-end collaboration Respond quickly to web page requests. It reduces the management and maintenance costs of front-end static resources for back-end developers, and improves the efficiency of Web page request response.

The Spring Boot framework is designed to simplify the initial setup and development of new Spring applications. The framework uses a specific approach to configuration, so that developers no longer need to define boilerplate configuration.

The JSch framework is a pure Java implementation of SSH2. It allows you to connect to an sshd server and perform specified functions using port forwarding, X11 forwarding, file transfer and other capabilities.

The response method of the Web page request provided by the present invention is applied to the back-end local server, and receives the Web page request sent by the front-end remote server; parses the Web page request to obtain the target static resource file to be obtained; utilizes the Spring Boot framework from Obtain the target static resource files in the back-end local preset directory, and use the target static resource files to build the service operating environment to respond to web page requests; among them, each static resource file in the back-end local preset directory is passed through JSch Frameworks are pulled from the front-end remote server. By pre-deploying the Spring Boot framework and the JSch framework, use the JSch framework to pre-pull each static resource file from the front-end remote server to the back-end local preset directory, and use the Spring Boot framework as a service proxy to obtain it from the back-end local preset directory Target static resource files, thereby reducing the management and maintenance costs of front-end static resources for back-end developers, and improving the efficiency of Web page request response.

It should be noted that, based on the first embodiment above, the embodiment of the present invention also provides a corresponding improvement solution. In subsequent embodiments, the same steps as in the first embodiment above or corresponding steps may be referred to each other, and the corresponding beneficial effects may also be referred to each other, and will not be repeated in the improved embodiments below.

Embodiment two:

Referring to Fig. 2, Fig. 2 is another implementation flowchart of the response method of the Web page request in the embodiment of the present invention, applied to the backend local server, the method may include the following steps:

S201: Receive a web page request sent by a front-end remote server.

S202: Analyzing the web page request to obtain the target static resource file to be obtained.

S203: Obtain the target static resource file from the backend local preset directory by using the Spring Boot framework.

S204: Utilize the Nginx reverse proxy server to reverse proxy the Spring Boot framework.

Pre-deploy the Nginx reverse proxy server and use the Nginx reverse proxy server to reverse proxy the SpringBoot framework. Therefore, there is no need for back-end developers to care about the storage location and subsequent changes of each static resource file in the front-end remote server, which improves the efficiency and success rate of file acquisition.

S205: Use the target static resource file to build a service operating environment to respond to the web page request.

Wherein, each static resource file in the back-end local default directory is pulled from the front-end remote server through the JSch framework.

S206: Respectively obtain the remote file update time corresponding to each static resource file in the front-end remote server, and the local file update time corresponding to each static resource file in the back-end local preset directory.

Each static resource file in the front-end remote server will be updated with business changes. To ensure the consistency of the front-end and back-end static resource files, each static resource file in the back-end local preset directory will also be updated accordingly. The remote file update time corresponding to each static resource file in the front-end remote server and the local file update time corresponding to each static resource file in the back-end local preset directory can be obtained in real time or according to a preset time interval.

S207: Determine whether there is a remote file update time greater than the corresponding local file update time in each remote file update time, if yes, perform step S208, if not, do not process.

After obtaining the remote file update time corresponding to each static resource file in the front-end remote server, and the local file update time corresponding to each static resource file in the back-end local preset directory, determine whether there is any remote file update time greater than The remote file update time of the corresponding local file update time. If yes, it means that there is a static resource file updated with respect to the back-end local preset directory in the front-end remote server, and then step S208 is executed. If not, it means that the current front-end remote server and The static resource files in the backend local preset directory are the same and do not need any processing.

S208: Determine the remote static resource file corresponding to the remote file update time greater than the corresponding local file update time as the target remote static resource file.

When it is determined that there is a remote file update time greater than the corresponding local file update time in each remote file update time, it means that there is a static resource file updated relative to the back-end local preset directory in the front-end remote server, which will be greater than the corresponding local file update time The remote static resource file corresponding to the remote file update time of time is determined as the target remote static resource file.

S209: Use the JSch framework to pull the target remote static resource file from the front-end remote server, so as to replace the corresponding static resource file in the back-end local preset directory with the target remote static resource file.

After determining the target remote static resource file, use the JSch framework to pull the target remote static resource file from the front-end remote server, and use the target remote static resource file to replace the corresponding static resource file in the back-end local preset directory, so that the front-end remote server Be consistent with the static resource files in the backend local preset directory.

S210: Traversing the full path file names corresponding to the respective static resource files in the backend local preset directory.

After the target remote static resource file is used to replace the corresponding static resource file in the backend local preset directory, the full path file names corresponding to the respective static resource files in the backend local preset directory are traversed.

S211: Determine whether each full-path file name exists in the full-path file name list, if yes, do not process, if not, execute step S212.

Wherein, the full path file name list is a list generated according to the survival status of each static resource file in the backend local preset directory.

Establish a full path file name list in advance according to the survival status of each static resource file in the back-end local default directory, and update the full path file name list according to the survival status update status of each static resource file in the back-end local default directory Update accordingly. After traversing the full-path file names corresponding to each static resource file in the back-end local default directory, determine whether each full-path file name exists in the full-path file name list. If so, it means this update of the front-end remote server If there is no static resource file deletion operation, no processing is performed. If not, it means that there is a static resource file deletion operation in this update of the front-end remote server, and step S212 is executed.

S212: Delete static resource files corresponding to full-path file names that do not exist in the full-path file name list in the backend local preset directory.

When it is determined that each full path file name exists in the full path file name list, it means that there is a static resource file deletion operation in the update of the front-end remote server, and the back-end local preset directory does not exist in the full path file name list Delete the static resource file corresponding to the full path file name.

This embodiment is different from Embodiment 1 corresponding to the technical solution claimed in independent claim 1, and also adds the technical solutions corresponding to the protected claims in dependent claims 2 to 5. Of course, according to different actual conditions and requirements, each The technical solutions required to be protected in the dependent claims are flexibly combined on the basis of not affecting the integrity of the solutions, so as to better meet the requirements of different usage scenarios. This embodiment only provides one of the solutions that contains the most solutions and has the best effect , because the situation is complicated, it is impossible to list all possible solutions. Those skilled in the art should be able to realize that there may be many examples based on the basic method principles provided by this application combined with actual situations. Without sufficient creative work, All should be within the scope of protection of this application.

Corresponding to the above method embodiment, the present invention also provides a Web page request response device, and the Web page request response device described below and the Web page request response device described above can be referred to in correspondence.

Referring to FIG. 3, FIG. 3 is a structural block diagram of a device for responding to a Web page request in an embodiment of the present invention, which is applied to a backend local server, and the device may include:

Request receiving module 31, is used for receiving the Web page request that front-end remote server sends;

The request parsing module 32 is used for parsing the Web page request to obtain the target static resource file to be acquired;

The request response module 33 is used to use the Spring Boot framework to obtain the target static resource file from the back-end local preset directory, and use the target static resource file to build a service operating environment to respond to the Web page request;

Wherein, each static resource file in the back-end local default directory is pulled from the front-end remote server through the JSch framework.

The response device for the Web page request provided by the present invention is applied to the back-end local server, and receives the Web page request sent by the front-end remote server; parses the Web page request to obtain the target static resource file to be obtained; utilizes the Spring Boot framework from Obtain the target static resource files in the back-end local preset directory, and use the target static resource files to build the service operating environment to respond to web page requests; among them, each static resource file in the back-end local preset directory is passed through JSch Frameworks are pulled from the front-end remote server. By pre-deploying the Spring Boot framework and the JSch framework, use the JSch framework to pre-pull each static resource file from the front-end remote server to the back-end local preset directory, and use the Spring Boot framework as a service proxy to obtain it from the back-end local preset directory Target static resource files, thereby reducing the management and maintenance costs of front-end static resources for back-end developers, and improving the efficiency of Web page request response.

In a specific embodiment of the present invention, the device may also include:

The reverse proxy module is used to use the Nginx reverse proxy server to reverse proxy the Spring Boot framework after using the Spring Boot framework to obtain the target static resources from the back-end local preset directory.

In a specific embodiment of the present invention, the device may also include:

The file update module is used to update each static resource file in the back-end local preset directory by using the JSch framework.

In a specific embodiment of the present invention, the file update module includes:

The update time acquisition sub-module is used to respectively acquire the remote file update time corresponding to each static resource file in the front-end remote server, and the local file update time corresponding to each static resource file in the back-end local preset directory;

The first judging submodule is used to judge whether there is a remote file update time greater than the corresponding local file update time in each remote file update time;

The target file determination sub-module is used to determine the remote static resource file corresponding to the remote file update time greater than the corresponding local file update time when it is determined that there is a remote file update time greater than the corresponding local file update time in each remote file update time Determined as the target remote static resource file;

The file replacement submodule is used to use the JSch framework to pull the target remote static resource file from the front-end remote server, so as to replace the corresponding static resource file in the back-end local preset directory with the target remote static resource file.

In a specific embodiment of the present invention, the file update module also includes:

The file name traversal sub-module is used to traverse the full path file names corresponding to each static resource file in the back-end local preset directory after replacing the corresponding static resource file in the back-end local preset directory with the target remote static resource file;

The second judging submodule is used to judge whether each full-path file name exists in the full-path file name list; wherein, the full-path file name list is generated according to the survival status of each static resource file in the back-end local preset directory list of;

The file deletion sub-module is used to delete the static files corresponding to the full-path file names in the back-end local preset directory that do not exist in the full-path file name list when it is determined that each full-path file name does not exist in the full-path file name list. Resource files are deleted.

Corresponding to the above method embodiment, referring to FIG. 4, FIG. 4 is a schematic diagram of a response device for a Web page request provided by the present invention, and the device may include:

Memory 41, used to store computer programs;

When the processor 42 is used to execute the computer program stored in the memory 41, the following steps can be realized:

Receive the web page request sent by the front-end remote server; parse the web page request to obtain the target static resource file; use the Spring Boot framework to obtain the target static resource file from the back-end local preset directory, and use the target static resource file Build a service running environment to respond to web page requests; among them, each static resource file in the back-end local preset directory is pulled from the front-end remote server through the JSch framework.

For the introduction of the device provided by the present invention, please refer to the above method embodiment, and the present invention will not repeat it here.

Corresponding to the above method embodiments, the present invention also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the following steps can be implemented:

Receive the web page request sent by the front-end remote server; parse the web page request to obtain the target static resource file; use the Spring Boot framework to obtain the target static resource file from the back-end local preset directory, and use the target static resource file Build a service running environment to respond to web page requests; among them, each static resource file in the back-end local preset directory is pulled from the front-end remote server through the JSch framework.

The computer-readable storage medium may include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk, etc., which can store program codes. medium.

For the introduction of the computer-readable storage medium provided by the present invention, please refer to the foregoing method embodiments, and the present invention will not repeat them here.

Each embodiment in this specification is described in a progressive manner, each embodiment focuses on the difference from other embodiments, and the same or similar parts of each embodiment can be referred to each other. As for the device, equipment and computer-readable storage medium disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and for relevant details, please refer to the description of the method part.

In this paper, specific examples are used to illustrate the principles and implementation methods of the present invention, and the descriptions of the above embodiments are only used to help understand the technical solutions and core ideas of the present invention. It should be pointed out that for those skilled in the art, without departing from the principle of the present invention, some improvements and modifications can be made to the present invention, and these improvements and modifications also fall within the protection scope of the claims of the present invention.

Claims (6)

1. A method for responding to a Web page request, characterized in that it is applied to a backend local server, comprising: Receive the web page request sent by the front-end remote server; Analyzing the web page request to obtain the target static resource file to be acquired; Using the Spring Boot framework to obtain the target static resource file from the back-end local preset directory, and using the target static resource file to build a service operating environment to respond to the Web page request; Wherein, each static resource file in the local default directory of the backend is obtained by pulling from the front-end remote server through the JSch framework; Traversing the full path file names corresponding to each of the static resource files in the back-end local preset directory; Judging whether each of the full-path file names exists in the full-path file name list; wherein, the full-path file name list is generated according to the survival status of each of the static resource files in the back-end local preset directory list of; If not, then delete the static resource files corresponding to the full-path file names that do not exist in the full-path file name list in the back-end local preset directory; Respectively obtain the remote file update time corresponding to each of the static resource files in the front-end remote server, and the local file update time corresponding to each of the static resource files in the back-end local preset directory; Judging whether there is a remote file update time greater than the corresponding local file update time in each of the remote file update times; If so, then determine the remote static resource file corresponding to the remote file update time greater than the corresponding local file update time as the target remote static resource file; Using the JSch framework to pull the target remote static resource file from the front-end remote server to replace the corresponding static resource file in the back-end local preset directory with the target remote static resource file. 2. the response method of Web page request according to claim 1, is characterized in that, after utilizing Spring Boot framework to obtain described target static resource from back-end local preset directory, also comprises: Use the Nginx reverse proxy server to reverse proxy the Spring Boot framework. 3. A response device for a Web page request, characterized in that it is applied to a backend local server, comprising: The request receiving module is used to receive the Web page request sent by the front-end remote server; A request parsing module, configured to parse the web page request to obtain the target static resource file to be acquired; The request response module is used to obtain the target static resource file from the back-end local preset directory by using the Spring Boot framework, and use the target static resource file to build a service operating environment to respond to the Web page request; Wherein, each static resource file in the local default directory of the backend is obtained by pulling from the front-end remote server through the JSch framework; A file update module, the file update module includes: The file name traversal sub-module is used to traverse the full path file names corresponding to each static resource file in the backend local preset directory; The second judging submodule is used to judge whether each full-path file name exists in the full-path file name list; wherein, the full-path file name list is generated according to the survival status of each static resource file in the back-end local preset directory list of; The file deletion sub-module is used to delete the static files corresponding to the full-path file names in the back-end local preset directory that do not exist in the full-path file name list when it is determined that each full-path file name does not exist in the full-path file name list. Resource file deletion; A file update module, the file update module includes an update time acquisition submodule, a first judgment submodule, a target file determination submodule and a file replacement submodule, and the update time acquisition submodule is used to acquire the front-end remote server respectively The remote file update time corresponding to each of the static resource files in , and the local file update time corresponding to each of the static resource files in the back-end local preset directory; The first judgment submodule is used to judge whether there is a remote file update time greater than the corresponding local file update time in each of the remote file update times; The target file determination submodule is configured to determine the remote file update time corresponding to the remote file update time greater than the corresponding local file update time when it is determined that there is a remote file update time greater than the corresponding local file update time in each of the remote file update times. The remote static resource file is determined as the target remote static resource file; The file replacement submodule is used to use the JSch framework to pull the target remote static resource file from the front-end remote server to replace the back-end local preset directory with the target remote static resource file Corresponding static resource files. 4. the response device of Web page request according to claim 3, is characterized in that, also comprises: The reverse proxy module is used to use the Nginx reverse proxy server to reverse proxy the Spring Boot framework after using the Spring Boot framework to obtain the target static resource from the backend local preset directory. 5. A response device for a Web page request, comprising: memory for storing computer programs; A processor, configured to implement the steps of the method for responding to a Web page request according to any one of claims 1 to 2 when executing the computer program. 6. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the Web page as described in any one of claims 1 to 2 is realized. The steps of the response method for the request.

Images