|
<AdminRoot "/usr/local/apache"> AdminAlias "My Favorite Server" TargetServerRoot "/usr/local/apache" TargetServerConfig conf/httpd_test.conf TargetAdminAllowDir /usr/local/apachea AdminAllowDir /usr/local/apacheb deep </AdminRoot>
Updates to Directories that configuration can access will generate an AdminAllowDir subdirective of AdminRoot. This is a directive that controls the directory access within the Administration Server GUI. The Administration Server will allow access to configuration data that is located in directories specified in the AdminAllowDir subdirective of AdminRoot.
There was a runtime error while STARTING or RESTARTING the IBM HTTP Server.
Check the messages returned from the server. If the message indicates that a directive may be misspelled or a module not loaded, you may assume that the module that processes the directive is not loaded. Here is an approach to detecting which module needs to be loaded:
Check the messages returned from the server. The name of the directive and the nature of the syntax error are described. To locate where the directive is set, and correct the error:
A scope is contained within an invalid parent scope. Scopes are organized as a hierarchical structure, and have the following valid hierarchical relationships:
The directory path specified cannot be located or cannot be parsed as a directory path.
The error may result because the file either does not exist or you do not have permission to access it. In addition to the access allowed within the Administration Server, your operating system may require directories and file permissions.
The file that you have attempted to access does not reside within a directory specified for access by the Administration Server. In Getting Started > Manage Servers, you can specify which directories in your file system can be accessed by the Administration Server. (Note: these settings are aside from any operating system access permissions that may be required.)
In addition to the access allowed within the Administration Server there may be directories and file permissions that are required.
The tasks are organized into associated directive settings that are valid within a defined scope or scopes. The following is a listing of all scopes that are valid for each task. (Tasks that are not constrained by scope are not listed.)
TASK NAME | VALID SCOPE(S) | |
Basic Settings
|
||
Core Settings: | <Global>, <Virtual Host> | |
Advanced Properties: | <Global> | |
Server Options: | all scopes except <Limit> and <SNMP> | |
Headers: | all scopes except <Limit> and <SNMP> | |
Cache Expiration: | all scopes except <Limit> and <SNMP> | |
Module Sequence: | <Global> | |
Additional Files: | <Global> | |
Machine Translation: | all scopes except <Limit> and <SNMP> | |
Meta Headers: | all scopes except <Limit> and <SNMP> | |
Indexing | ||
Options: | <Global>, <Virtual Host>, <Directory>, <Directory Match> | |
Files: | <Global>, <Virtual Host>, <Directory>, <Directory Match> | |
Icons: | <Global>, <Virtual Host>, <Directory>, <Directory Match> | |
File Descriptions: | <Global>, <Virtual Host>, <Directory>, <Directory Match> | |
Icon Descriptions: | <Global>, <Virtual Host>, <Directory>, <Directory Match> | |
Access Permissions | ||
General Access: | <Directory>, <Directory Match>, <Files>, <Files Match>, <Location>, <Location Match>, <Limit> | |
Individual Access: | <Directory>, <Directory Match>, <Files>, <Files Match>, <Location>, <Location Match>, <Limit> | |
Group Access: | <Directory>, <Directory Match>, <Files>, <Files Match>, <Location>, <Location Match>, <Limit> | |
Other Access: | <Directory>, <Directory Match>, <Files>, <Files Match>, <Location>, <Location Match>, <Limit> | |
Anonymous Access: | <Directory>, <Directory Match>, <Files>, <Files Match>, <Location>, <Location Match>, <Limit> | |
Security | ||
Server Security: | <Global> | |
Host Authorization: | <Virtual Host> | |
Directory Authorization: | <Directory>, <Directory Match> | |
Logs | ||
Main Logs: | <Global>, <Virtual Host> | |
Other Logs: | <Global>, <Virtual Host> | |
Directory Logging: | all scopes except <Limit> and <SNMP> | |
View Logs: | <Global>, <Virtual Host> | |
Mappings | ||
Messages: | all scopes except <Limit> and <SNMP> | |
Aliases: | <Global>, <Virtual Host> | |
Redirects: | <Global>, <Virtual Host> | |
Username Directories: | <Global>, <Virtual Host> | |
Scripts | ||
Associate Actions: | all scopes except <Limit> and <SNMP> | |
Define Variables: | <Global>, <Virtual Host> | |
Unset Variables: | <Global>, <Virtual Host> | |
Conditional Variables: | <Global> | |
Browser Detection: | <Global> | |
Performance | ||
Server Settings: | <Global> | |
Set Cache: | <Virtual Host>, <Directory>, <Directory Match>, <Location>, <Location Match> | |
SNMP: | <SNMP> | |
MIME | ||
MIME Files: | all scopes except <Limit> and <SNMP> | |
MIME Types: | all scopes except <Limit> and <SNMP> | |
MIME Encodings: | all scopes except <Limit> and <SNMP> | |
Document Handlers: | all scopes except <Limit> and <SNMP> | |
Remove Handlers: | <Directory>, <Directory Match>, <Files>, <Files Match>, <Location>, <Location Match> | |
Language Files: | all scopes except <Limit> and <SNMP> | |
Type Handling: | <Directory>, <Directory Match>, <Files>, <Files Match>, <Location>, <Location Match> | |
Fast CGI | ||
Internal Server: | <Global>, <Virtual Host> | |
Configuration: | <Global> | |
External Server: | <Global> | |
Access: | <Directory>, <Directory Match> | |
File Systems | ||
Enable DAV: | <Directory>, <Directory Match>, <Files>, <Files Match>, <Location>, <Location Match> | |
DAV Settings: | <Global>, <Virtual Host> | |
Proxy | ||
Proxy Cache: | <Global>, <Virtual Host> | |
Proxy Settings: | <Global>, <Virtual Host> | |
View Configuration | ||
Edit Configuration: | all scopes |
No directory has been specified for access by the Administration Server. In Getting Started > Manage Servers, you can specify which directories in your file system can be accessed by the Administration Server. (Note: these settings are aside from any operating system access permissions that may be required.)