The software described in this documentation is either in Extended Support or Sustaining Support. See https://www.oracle.com/us/support/library/enterprise-linux-support-policies-069172.pdf for more information.
Oracle recommends that you upgrade the software described by this documentation as soon as possible.
The following example illustrates how you can nest containers,
using <Limit> and
<LimitExcept> containers to permit
GET, POST, and
OPTIONS to be used with user directories
under /home/*/public_html.
<Directory /home/*/public_html>
AllowOverride FileInfo AuthConfig Limit
Options MultiViews Indexes SymLinksIfOwnerMatch \
IncludesNoExec
<Limit GET POST OPTIONS>
Order allow,deny
Allow from all
</Limit>
<LimitExcept GET POST OPTIONS>
Order deny,allow
Deny from all
</LimitExcept>
</Directory>
In the example, the AllowOverride directive
specifies the following directive classes:
-
AuthConfig Permits the use of the authorization directives.
-
FileInfo Permits the use of directives that control document types.
-
Limit Permits the use of directives that control host access.
The Options directive controls the features
of the server for the directory hierarchy, for example:
-
FollowSymLinks Follow symbolic links under the directory hierarchy.
-
Includes Permits server-side includes.
-
IncludesNoExec Prevents the server from running
#exec cmdand#exec cgiserver-side includes.-
Indexes Generates a web directory listing if the
DirectoryIndexdirective is not set.-
MultiViews Allows the server to determine the file to use that best matches the client's requirements based on the MIME type when several versions of the file exist with different extensions.
-
SymLinksIfOwnerMatch Allows the server to follow a symbolic link if the file or directory being pointed to has the same owner as the symbolic link.
For more information, see http://httpd.apache.org/docs/current/mod/directives.html.

