Shulou(Shulou.com)06/03 Report--

5. HTTP request processing related configuration file description

The whole space of HTTP request is layered, including Web container, Web application, Spring framework and so on. Each layer is initialized by configuration file, which is a loosely coupled architecture design. Now let's comb through these configuration files. The HTTP request traverses the Web container first. The configuration file that represents the product Tomcat is: server.xml.

The second path traverses the Web application, which is composed of components such as Listener\ Filter\ Servlet. The main configuration file is: web.xml

The third path traverses the Spring framework, which is divided into three layers: presentation layer, domain layer and data source layer, which are also configured and maintained by different configuration files. The presentation layer is through mvc-servlet.xml, the domain layer is through applicationContext.xml, and the data source layer is configured and assembled through the configuration files sqlmap-mapping.xml, jdbc.properties, etc., of the object relational mapping framework ORM (Hibernate\ iBatis\ MyBatis, etc.) For specific correspondence, please refer to the following figure:

The reason why I introduce this part of the content is to help you build a concept. The whole system is built from the outside to the inside, and the interior of each layer is built by different types of components like building blocks. Layer to layer and inside each layer are connected through configuration files. If you want to have a more systematic and in-depth understanding of the entire application architecture, we can use the above configuration files as an entry point or clue. Considering that the topic of this article is to analyze the processing mechanism of HTTP requests, we will not discuss it any more.

6. Description of frequently asked questions about HTTP request processing

In daily system development or maintenance, most of the problems are related to HTTP request processing. Part of it is that we are not familiar with the HTTP protocol itself. HTTP protocol is the most important application layer protocol for the integration of various systems in the Internet. The design of the protocol is very good. We can take some time to study this protocol in depth. Of course, if we have time to attach the TCP/IP protocol, especially the various types of parameters that control the quality of service in the protocol.

In addition, most of them are not familiar with the whole process of HTTP request processing, do not know in which link to set debugging breakpoints, and do not fill in configuration files as required, so it is easy to get into a maze and spend a lot of time and energy to find clues.

The main value of this article is to help you sort out the end-to-end framework of the whole process, that is, the global perspective or God perspective. With this framework, we can according to our own needs to find clues to find the relevant node information to study, so as not to fall into the details can not find the direction.

Of course, considering that each of us has different work and study conditions and different problems we usually encounter, this article cannot cover all the problems encountered by us. You are welcome to leave messages and ask questions. You are welcome to follow my official Wechat account "IT veteran" for communication and interaction. I will try my best to answer your questions as soon as possible. Thank you!

The index of other articles in this series is as follows:

Diagram Spring:HTTP request processing flow and mechanism [1] diagram Spring:HTTP request processing flow and mechanism [2] diagram Spring:HTTP request processing flow and mechanism [3] diagram Spring:HTTP request processing flow and mechanism [4]

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.