Engine

最新推荐文章于 2022-06-06 16:48:03 发布

原创最新推荐文章于 2022-06-06 16:48:03 发布 · 944 阅读

0 ·

CC 4.0 BY-SA版权

文章标签：

#servlet #containers #wrapper #server #types #apache

Java 专栏收录该内容

35 篇文章

订阅专栏

博客介绍了使用拦截器查看引擎处理的每个请求，以及在独立HTTP连接器中运行Catalina并支持多虚拟主机。还提到Engine下可配置多个虚拟主机，请求会匹配到相应Host处理，若无法匹配则交给默认Host。

An Engine is a Container that represents the entire Catalina servlet engine. It is useful in the following types of scenarios:

You wish to use Interceptors that see every single request processed by the entire engine.
You wish to run Catalina in with a standalone HTTP connector, but still want support for multiple virtual hosts.

In general, you would not use an Engine when deploying Catalina connected to a web server (such as Apache), because the Connector will have utilized the web server's facilities to determine which Context (or perhaps even which Wrapper) should be utilized to process this request.

The child containers attached to an Engine are generally implementations of Host (representing a virtual host) or Context (representing individual an individual servlet context), depending upon the Engine implementation.

If used, an Engine is always the top level Container in a Catalina hierarchy. Therefore, the implementation's setParent() method should throw IllegalArgumentException.

Engine下可以配置多个虚拟主机Virtual Host，每个虚拟主机都有一个域名

当Engine获得一个请求时，它把该请求匹配到某个Host上，然后把该请求交给该Host来处理 Engine有一个默认虚拟主机，当请求无法匹配到任何一个Host上的时候，将交给该默认Host来处理