Scope of Configuration
RSRC_CONF:httpd.conf at top level or in a VirtualHost context. All directives using server configuration should use this option, as other
contexts are meaningless for a server configuration.
ACCESS_CONF:httpd.conf in a directory context. This option is appropriate to per-directory configuration directives for a server administrator
only. It is often combined (using OR) with RSRC_CONF to allow its use anywhere within httpd.conf, giving rise to the “gotcha” mentioned earlier
related to directives appearing in ambiguous contexts.
OR_LIMIT, OR_OPTIONS, OR_FILEINFO, OR_AUTHCFG, OR_INDEXES: extend ACCESS_CONF to allow use of the directive in .htaccess, where permitted by
the AllowOverride setting.
An additional value, EXEC_ON_READ, can be ORed with any of the preceding options to take control of parsing httpd.conf into a module.
Configuration Function Types
This is one of several such macros defined in http_config.h:
AP_INIT_NO_ARGS--no arguments
AP_INIT_FLAG--a single On/Off argument
AP_INIT_TAKE1--a single string, file or numeric argument
AP_INIT_TAKE2, AP_INIT_TAKE3--two/three arguments
AP_INIT_TAKE12, and so on--directives taking variable numbers of arguments
AP_INIT_ITERATE--function will be called repeatedly with each of an unspecified number of arguments
AP_INIT_ITERATE2--function will be called repeatedly with two arguments
AP_INIT_RAW_ARGS--function will be called with arguments unprocessed
Last night I studied how to implement an embeded OS again. I almost took one year to study it. The principle of threads and the critional
section, and how to boot a system, the mechanism of building device database, and the architecture of device driver, and so on. Those all are
important to a programmer. Those are fundmental knowledge.
I can go inside an system. It is a good example to understand others.
RSRC_CONF:httpd.conf at top level or in a VirtualHost context. All directives using server configuration should use this option, as other
contexts are meaningless for a server configuration.
ACCESS_CONF:httpd.conf in a directory context. This option is appropriate to per-directory configuration directives for a server administrator
only. It is often combined (using OR) with RSRC_CONF to allow its use anywhere within httpd.conf, giving rise to the “gotcha” mentioned earlier
related to directives appearing in ambiguous contexts.
OR_LIMIT, OR_OPTIONS, OR_FILEINFO, OR_AUTHCFG, OR_INDEXES: extend ACCESS_CONF to allow use of the directive in .htaccess, where permitted by
the AllowOverride setting.
An additional value, EXEC_ON_READ, can be ORed with any of the preceding options to take control of parsing httpd.conf into a module.
Configuration Function Types
This is one of several such macros defined in http_config.h:
AP_INIT_NO_ARGS--no arguments
AP_INIT_FLAG--a single On/Off argument
AP_INIT_TAKE1--a single string, file or numeric argument
AP_INIT_TAKE2, AP_INIT_TAKE3--two/three arguments
AP_INIT_TAKE12, and so on--directives taking variable numbers of arguments
AP_INIT_ITERATE--function will be called repeatedly with each of an unspecified number of arguments
AP_INIT_ITERATE2--function will be called repeatedly with two arguments
AP_INIT_RAW_ARGS--function will be called with arguments unprocessed
Last night I studied how to implement an embeded OS again. I almost took one year to study it. The principle of threads and the critional
section, and how to boot a system, the mechanism of building device database, and the architecture of device driver, and so on. Those all are
important to a programmer. Those are fundmental knowledge.
I can go inside an system. It is a good example to understand others.
扫一扫
5318
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
