#include <http_config.h>
変数 | |
| void * | info |
| int | override |
| apr_int64_t | limited |
| apr_array_header_t * | limited_xmethods |
| ap_method_list_t * | xlimited |
| ap_configfile_t * | config_file |
| ap_directive_t * | directive |
| apr_pool_t * | pool |
| apr_pool_t * | temp_pool |
| server_rec * | server |
| char * | path |
| const command_rec * | cmd |
| ap_conf_vector_t * | context |
| const ap_directive_t * | err_directive |
| int | override_opts |
| const command_rec* cmd_parms_struct::cmd |
configuration command
Config file structure.
per_dir_config vector passed to handle_command
the directive specifying this command
directive with syntax error
| void* cmd_parms_struct::info |
Argument to command from cmd_table
| apr_int64_t cmd_parms_struct::limited |
Which methods are <Limit>ed
methods which are limited
Which allow-override bits are set
Which allow-override-opts bits are set
| char* cmd_parms_struct::path |
If configuring for a directory, pathname of that directory. NOPE! That's what it meant previous to the existance of <Files>, <Location> and regex matching. Now the only usefulness that can be derived from this field is whether a command is being called in a server context (path == NULL) or being called in a dir context (path != NULL).
Pool to allocate new storage in
Server_rec being configured for
Pool for scratch memory; persists during configuration, but wiped before the first request is served...
methods which are xlimited
1.4.7