December 20th Thursday (十二月 二十日 木曜日)

   AP_INIT_TAKE1 is one of many such macros, all having the same prototype (more on that later). It has the following arguments:
1. Directive name
2. Function implementing the directive NULL)
3. Data pointer (often
4. Context in which this directive is allowed
5. A brief help message for the directive

  Normal behavior in the directory hierarchy meets the following criteria:

1. Any applicable <Directory> or <Location> overrides a configuration that isn’t in any container.

2. A .htaccess file (if enabled) overrides httpd.conf for the same directory.

3. A directory’s configuration overrides a parent directory’s configuration.

4. Any applicable <Location> overrides <Files>, which overrides <Directory> and .htaccess.

5. The <Location> and<Files> containers override each other based not on specificity, but rather on
the order in which they appear in httpd.conf.

6. Where configuration values are not explicitly set, they are inherited rather than overridden.

7. These relationships may be influenced by a module such as mod_alias hooking a relevant function before the map_to_storage phase.

NOT_IN_VIRTUALHOST is one of several macros we can test in this manner. Others NOT_IN_LIMIT,NOT_IN_DIRECTORY,NOT_IN_LOCATION,NOT_IN_FILES,
include NOT_IN_DIR_LOC_FILE, and GLOBAL_ONLY. These macros can be used with a logical OR, and ap_check_cmd_context will return NULL if and
only if the conditions are satisfied.