Module Configuration
Table of Contents
Module | Is Internal | Module Parameters | Enable Hooks | Hook::L4_BEGINSESSION Priority | Hook::L4_ENDSESSION Priority | Hook::L4_RECVING Priority | Hook::L4_SENDING Priority | Hook::HTTP_BEGIN Priority | Hook::RECV_REQ_HEADER Priority | Hook::URI_MAP Priority | Hook::HTTP_AUTH Priority | Hook::RECV_REQ_BODY Priority | Hook::RCVD_REQ_BODY Priority | Hook::RECV_RESP_HEADER Priority | Hook::RECV_RESP_BODY Priority | Hook::RCVD_RESP_BODY Priority | Hook::HANDLER_RESTART Priority | Hook::SEND_RESP_HEADER Priority | Hook::SEND_RESP_BODY Priority | Hook::HTTP_END Priority | Hook::MAIN_INITED Priority | Hook::MAIN_PREFORK Priority | Hook::MAIN_POSTFORK Priority | Hook::WORKER_POSTFORK Priority | Hook::WORKER_ATEXIT Priority | Hook::MAIN_ATEXIT Priority
URI | Module | Extra Headers | Realm | 认证名称 | Require(授权的用户/组) | 允许访问列表 | 拒绝访问列表 | Authorizer | 添加默认的字符集 | 自定义默认字符集 | 启用IP地理定位
Server Modules⇑
Description
The Server module configuration globally defines the module configuration data. Once defined, the Listeners and Virtual Hosts have access to the modules and module configurations.
All modules that are to be processed must be registered in the Server configuration. The Server configuration also defines the default values for module parameter data. These values can be inherited or overridden by the Listener and Virtual Host configuration data.
Module priority is only defined at server level and is inherited by the Listener and Virtual Host configurations.
Module⇑
Description
Name of the module. The module name will be the same as the module filename. The module file must be located under $SERVER_ROOT/modules/modulename.so in order to be loaded by the server application. The server will load the registered modules at start up. This requires that the server is restarted after new modules are registered.
Syntax
the library name of .so.
Is Internal⇑
Description
Specify whether the module is an internal module, which is staticaly linked, instead of being an external .so library.
Syntax
Select from radio box
Module Parameters⇑
Description
Set module parameters. The module parameters are defined by the module developer.
Set the value in the Server configuration to globally assign the default value. The user can override this setting at the Listener, Virtual Host or Context levels. If the 'Not Set' radio button is selected, it will be inherited from the upper level.
Syntax
Specified by the module interface.
Enable Hooks⇑
Description
Enables or disables the module hooks globally.
If the 'Not Set' radio button is selected and the module contains hook functions, the default is enabled. The user can override this global setting at each level.
Syntax
Select from radio box
Hook::L4_BEGINSESSION Priority⇑
Description
Sets the priority for this module callback within the L4 Begin Session Hook.
The L4 Begin Session Hook is triggered when the TCP/IP connection begins.
It will only take effect if the module has a hook point here. If it is not set, the priority will be the default value defined in the module.
Syntax
Integer value from -6000 to 6000. Lower value means higher priority.
Hook::L4_ENDSESSION Priority⇑
Description
Sets the priority for this module callback within the L4 End Session Hook.
The L4 End Session Hook is triggered when the TCP/IP connection ends.
It will only take effect if the module has a hook point here. If it is not set, the priority will be the default value defined in the module.
Syntax
Integer value from -6000 to 6000. Lower value means higher priority.
Hook::L4_RECVING Priority⇑
Description
Sets the priority for this module callback within the L4 Receiving Hook.
The L4 Receiving Hook is triggered when the TCP/IP connection receives data.
It will only take effect if the module has a hook point here. If it is not set, the priority will be the default value defined in the module.
Syntax
Integer value from -6000 to 6000. Lower value means higher priority.
Hook::L4_SENDING Priority⇑
Description
Sets the priority for this module callback within the L4 Sending Hook.
The L4 Sending Hook is triggered when the TCP/IP connection sends data.
It will only take effect if the module has a hook point here. If it is not set, the priority will be the default value defined in the module.
Syntax
Integer value from -6000 to 6000. Lower value means higher priority.
Hook::HTTP_BEGIN Priority⇑
Description
Sets the priority for this module callback within the HTTP Begin Hook.
The HTTP Begin Hook is triggered when the TCP/IP connection begins an HTTP Session.
It will only take effect if the module has a hook point here. If it is not set, the priority will be the default value defined in the module.
Syntax
Integer value from -6000 to 6000. Lower value means higher priority.
Hook::RECV_REQ_HEADER Priority⇑
Description
Sets the priority for this module callback within the HTTP Receive Request Header Hook.
The HTTP Receive Request Header Hook is triggered when the web server receives a request header.
It will only take effect if the module has a hook point here. If it is not set, the priority will be the default value defined in the module.
Syntax
Integer value from -6000 to 6000. Lower value means higher priority.
Hook::URI_MAP Priority⇑
Description
Sets the priority for this module callback within the HTTP URI Map Hook.
The HTTP URI Map Hook is triggered when the web server maps a URI request to a context.
It will only take effect if the module has a hook point here. If it is not set, the priority will be the default value defined in the module.
Syntax
Integer value from -6000 to 6000. Lower value means higher priority.
Hook::HTTP_AUTH Priority⇑
Description
Sets the priority for this module callback within the HTTP Authentication Hook.
The HTTP Authentication Hook is triggered after resource mapping and before handler processing. It occurs after HTTP built-in authentication, and can be used to perform additional authentication checking.
It will only take effect if the module has a hook point here. If it is not set, the priority will be the default value defined in the module.
Syntax
Integer value from -6000 to 6000. Lower value means higher priority.
Hook::RECV_REQ_BODY Priority⇑
Description
Sets the priority for this module callback within the HTTP Receive Request Body Hook.
The HTTP Receive Request Body Hook is triggered when the web server receives request body data.
It will only take effect if the module has a hook point here. If it is not set, the priority will be the default value defined in the module.
Syntax
Integer value from -6000 to 6000. Lower value means higher priority.
Hook::RCVD_REQ_BODY Priority⇑
Description
Sets the priority for this module callback within the HTTP Received Request Body Hook.
The HTTP Received Request Body Hook is triggered when the web server finishes receiving request body data.
It will only take effect if the module has a hook point here. If it is not set, the priority will be the default value defined in the module.
Syntax
Integer value from -6000 to 6000. Lower value means higher priority.
Hook::RECV_RESP_HEADER Priority⇑
Description
Sets the priority for this module callback within the HTTP Receive Response Header Hook.
The HTTP Receive Response Header Hook is triggered when the web server creates the response header.
It will only take effect if the module has a hook point here. If it is not set, the priority will be the default value defined in the module.
Syntax
Integer value from -6000 to 6000. Lower value means higher priority.
Hook::RECV_RESP_BODY Priority⇑
Description
Sets the priority for this module callback within the HTTP Receive Response Body Hook.
The HTTP Receive Response Body Hook is triggered when the web server backend receives the response body.
It will only take effect if the module has a hook point here. If it is not set, the priority will be the default value defined in the module.
Syntax
Integer value from -6000 to 6000. Lower value means higher priority.
Hook::RCVD_RESP_BODY Priority⇑
Description
Sets the priority for this module callback within the HTTP Received Response Body Hook.
The HTTP Received Response Body Hook is triggered when the web server backend finishes receiving the response body.
It will only take effect if the module has a hook point here. If it is not set, the priority will be the default value defined in the module.
Syntax
Integer value from -6000 to 6000. Lower value means higher priority.
Hook::HANDLER_RESTART Priority⇑
Description
Sets the priority for this module callback within the HTTP Handler Restart Hook.
The HTTP Handler Restart Hook is triggered when the web server needs to discard the current response and start processing from beginning, for example, when an internal redirect has been requested.
It will only take effect if the module has a hook point here. If it is not set, the priority will be the default value defined in the module.
Syntax
Integer value from -6000 to 6000. Lower value means higher priority.
Hook::SEND_RESP_HEADER Priority⇑
Description
Sets the priority for this module callback within the HTTP Send Response Header Hook.
The HTTP Send Response Header Hook is triggered when the web server is ready to send the response header.
It will only take effect if the module has a hook point here. If it is not set, the priority will be the default value defined in the module.
Syntax
Integer value from -6000 to 6000. Lower value means higher priority.
Hook::SEND_RESP_BODY Priority⇑
Description
Sets the priority for this module callback within the HTTP Send Response Body Hook.
The HTTP Send Response Body Hook is triggered when the web server is going to send the response body.
It will only take effect if the module has a hook point here. If it is not set, the priority will be the default value defined in the module.
Syntax
Integer value from -6000 to 6000. Lower value means higher priority.
Hook::HTTP_END Priority⇑
Description
Sets the priority for this module callback within the HTTP Session End Hook.
The HTTP Session End Hook is triggered when the HTTP connection has ended.
It will only take effect if the module has a hook point here. If it is not set, the priority will be the default value defined in the module.
Syntax
Integer value from -6000 to 6000. Lower value means higher priority.
Hook::MAIN_INITED Priority⇑
Description
Sets the priority for this module callback within the Main Initialized Hook.
The Main Initialized Hook is triggered once upon startup, after the server configuration and initialization is completed by the main (controller) process, and before any requests are serviced.
It will only take effect if the module has a hook point here. If it is not set, the priority will be the default value defined in the module.
Syntax
Integer value from -6000 to 6000. Lower value means higher priority.
Hook::MAIN_PREFORK Priority⇑
Description
Sets the priority for this module callback within the Main Prefork Hook.
The Main Prefork Hook is triggered by the main (controller) process immediately before a new worker process is started (forked). This is called for each worker, and may happen during system startup, or if a worker has been restarted.
It will only take effect if the module has a hook point here. If it is not set, the priority will be the default value defined in the module.
Syntax
Integer value from -6000 to 6000. Lower value means higher priority.
Hook::MAIN_POSTFORK Priority⇑
Description
Sets the priority for this module callback within the Main Postfork Hook.
The Main Postfork Hook is triggered by the main (controller) process immediately after a new worker process has been started (forked). This is called for each worker, and may happen during system startup, or if a worker has been restarted.
It will only take effect if the module has a hook point here. If it is not set, the priority will be the default value defined in the module.
Syntax
Integer value from -6000 to 6000. Lower value means higher priority.
Hook::WORKER_POSTFORK Priority⇑
Description
Sets the priority for this module callback within the Worker Postfork Hook.
The Worker Postfork Hook is triggered by a worker process after being created by the main (controller) process. Note that a corresponding Main Postfork Hook may be called by the main process either before or after this callback.
It will only take effect if the module has a hook point here. If it is not set, the priority will be the default value defined in the module.
Syntax
Integer value from -6000 to 6000. Lower value means higher priority.
Hook::WORKER_ATEXIT Priority⇑
Description
Sets the priority for this module callback within the Worker At Exit Hook.
The Worker At Exit Hook is triggered by a worker process just prior to exiting. It is the last hook point to be called by a worker.
It will only take effect if the module has a hook point here. If it is not set, the priority will be the default value defined in the module.
Syntax
Integer value from -6000 to 6000. Lower value means higher priority.
Hook::MAIN_ATEXIT Priority⇑
Description
Sets the priority for this module callback within the Main At Exit Hook.
The Main At Exit Hook is triggered by the main (controller) process just prior to exiting. It is the last hook point to be called by the main process.
It will only take effect if the module has a hook point here. If it is not set, the priority will be the default value defined in the module.
Syntax
Integer value from -6000 to 6000. Lower value means higher priority.
Listener Modules⇑
Description
Listener module configuration data is, by default inherited from the Server module configuration. The Listener Modules are limited to the TCP/IP Layer 4 hooks.
Enable Hooks⇑
Description
Enables or disables the module hooks at the Listener level. Only if the module has TCP/IP level hooks (L4_BEGSESSION, L4_ENDSESSION, L4_RECVING, L4_SENDING), this setting will take effect.
If the 'Not Set' radio button is selected, the default will be inherited from the Server configuration. The user only needs to set it here to override the default settings.
Syntax
Select from radio box
Virtual Host Modules⇑
Description
Virtual Host module configuration data is, by default inherited from the Server module configuration. The Virtual Host Modules are limited to the HTTP level hooks.
Enable Hooks⇑
Description
Enables or disables the module hooks at the Virtual Host or Context level. Only if the module has HTTP level hooks, this setting will take effect.
If the 'Not Set' radio button is selected, the Virtual Host level default settings will be inherited from the Server configuration. Context level settings will be inherited from the Virtual Host level. The user only needs to set it here to override the default settings.
Syntax
Select from radio box
Virtual Host Module Context⇑
Description
It's a centralized place to customize module settings for virtual host contexts. Settings for a context URI will override the virtual host or the server level settings.
URI⇑
Description
Specifies the URI for this context.
Syntax
The URI can be a plain URI (starting with "/") or a Perl compatible regular expression URI (starting with "exp:"). If a plain URI ends with a "/", then this context will include all sub-URIs under this URI. If the context maps to a directory on the file system, a trailing "/" must be added.
See Also
Module Handler Context⇑
Description
A module handler context will associate a URI with a registered module. Modules need to be registered at Server Module Configuration tab.
Module⇑
Description
Name of the module. The module must be registered under the Server Module Configuration tab. Once it is registered, the module name will be available in the drop down box for the Listener and Virtual Host configurations.
Syntax
Select from drop down list
Extra Headers⇑
Description
Specifies extra response headers to be added. Multiple headers can be added, one header per line. Put "NONE" to disable headers inherited from parent content.
Syntax
"[HeaderName]: [HeaderValue]" in each line.
Example
My-header: Custom header value
Realm⇑
Description
指定这个context下的realm授权。 当指定时,必须提供有效的用户和用户名来访问这个context。 Realms授权需要在Virtual Host Security部分进行设置。此设置使用每个realm的Realm名称。
Syntax
选项
认证名称⇑
Description
为当前context下的realm认证指定一个替代的名称。 如果没有指定,原realm名称将被使用。 认证名称将显示在浏览器登陆弹出窗口。
Syntax
文本
Require(授权的用户/组)⇑
Description
指定哪些用户/用户组可以访问此context。 这里允许你使用一个用户/组数据库(在 Realm中指定)访问多个context, 但只允许该数据库下特定的用户/组访问这个context。
Syntax
语法兼容Apache的Require指令。例如:
- user username [username ...]
只有列出的用户可以访问这个context; - group groupid [groupid ...]
用户必须属于列出的组才可以访问这个context。
允许访问列表⇑
Description
指定允许访问这个context下资源的IP地址或子网。综合 拒绝访问列表项的配置以及服务器/虚拟主机级别访问控制, 可访问性将以客户端IP所符合的最小范围来确定。
Syntax
逗号分隔的IP地址/子网列表。
Example
拒绝访问列表⇑
Description
指定哪个IP地址或子网不被允许访问这个context下的资源。 综合允许访问列表项的配置以及服务器/虚拟主机级别访问控制, 可访问性将以客户端IP所符合的最小范围来确定。
Syntax
逗号分隔的IP地址/子网列表。
Example
Authorizer⇑
Description
Specifies an external application that can be used to generate authorized/unauthorized decisions. Currently, only the FastCGI Authorizer is available. For more details about the FastCGI Authorizer role, please visit http://www.fastcgi.com.
Syntax
Select from drop down list
添加默认的字符集⇑
Description
指定当内容类型是"text/html"或"text/plain"且没有参数时,是否添加字符集标记到"Content-Type"响应报头中。当设置为Off时,该功能禁用。当设置为On时,将添加自定义默认字符集中指定的字符集,如果没有指定,将添加默认的"iso-8859-1"字符集。
Syntax
布尔值
自定义默认字符集⇑
Description
指定一个字符集当添加默认的字符集是On时使用。这是可选的。默认值是iso-8859-1。当添加默认的字符集是Off时本设置将不生效。
Syntax
字符集的名称,例如utf-8
Example
启用IP地理定位⇑
Description
指定是否启用IP地理定位查找。 可以在服务器级别,虚拟主机级别,或context级别设置。
Syntax
布尔值