[apache] “이 서버에 액세스 할 수있는 권한이 없습니다”라는 오류 메시지가 표시됨

Apache를 직접 구성 하고 가상 호스트에 phpMyAdmin 을로드하려고했지만 다음과 같은 메시지가 나타납니다 .

403 금지이 서버에 액세스 할 수있는 권한이 없습니다

내 httpd.conf

#
# This is the main Apache HTTP server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.2> for detailed information.
# In particular, see
# <URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
# for a discussion of each configuration directive.
#
# Do NOT simply read the instructions in here without understanding
# what they do.  They're here only as hints or reminders.  If you are unsure
# consult the online docs. You have been warned.
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path.  If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
# with ServerRoot set to "C:/Program Files (x86)/Apache Software Foundation/Apache2.2" will be interpreted by the
# server as "C:/Program Files (x86)/Apache Software Foundation/Apache2.2/logs/foo.log".
#
# NOTE: Where filenames are specified, you must use forward slashes
# instead of backslashes (e.g., "c:/apache" instead of "c:\apache").
# If a drive letter is omitted, the drive on which httpd.exe is located
# will be used by default.  It is recommended that you always supply
# an explicit drive letter in absolute paths to avoid confusion.

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# Do not add a slash at the end of the directory path.  If you point
# ServerRoot at a non-local disk, be sure to point the LockFile directive
# at a local disk.  If you wish to share the same ServerRoot for multiple
# httpd daemons, you will need to change at least LockFile and PidFile.
#
ServerRoot "C:/Program Files (x86)/Apache Software Foundation/Apache2.2"

#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
#
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses.
#
#Listen 12.34.56.78:80
Listen 127.0.0.1:80

Include conf/vhosts.conf

#
# Dynamic Shared Object (DSO) Support
#
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
#
# Example:
# LoadModule foo_module modules/mod_foo.so
#
LoadModule actions_module modules/mod_actions.so
LoadModule alias_module modules/mod_alias.so
LoadModule asis_module modules/mod_asis.so
LoadModule auth_basic_module modules/mod_auth_basic.so
#LoadModule auth_digest_module modules/mod_auth_digest.so
#LoadModule authn_alias_module modules/mod_authn_alias.so
#LoadModule authn_anon_module modules/mod_authn_anon.so
#LoadModule authn_dbd_module modules/mod_authn_dbd.so
#LoadModule authn_dbm_module modules/mod_authn_dbm.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule authn_file_module modules/mod_authn_file.so
#LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
#LoadModule authz_dbm_module modules/mod_authz_dbm.so
LoadModule authz_default_module modules/mod_authz_default.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_host_module modules/mod_authz_host.so
#LoadModule authz_owner_module modules/mod_authz_owner.so
LoadModule authz_user_module modules/mod_authz_user.so
LoadModule autoindex_module modules/mod_autoindex.so
#LoadModule cache_module modules/mod_cache.so
#LoadModule cern_meta_module modules/mod_cern_meta.so
LoadModule cgi_module modules/mod_cgi.so
#LoadModule charset_lite_module modules/mod_charset_lite.so
#LoadModule dav_module modules/mod_dav.so
#LoadModule dav_fs_module modules/mod_dav_fs.so
#LoadModule dav_lock_module modules/mod_dav_lock.so
#LoadModule dbd_module modules/mod_dbd.so
#LoadModule deflate_module modules/mod_deflate.so
LoadModule dir_module modules/mod_dir.so
#LoadModule disk_cache_module modules/mod_disk_cache.so
#LoadModule dumpio_module modules/mod_dumpio.so
LoadModule env_module modules/mod_env.so
#LoadModule expires_module modules/mod_expires.so
#LoadModule ext_filter_module modules/mod_ext_filter.so
#LoadModule file_cache_module modules/mod_file_cache.so
#LoadModule filter_module modules/mod_filter.so
#LoadModule headers_module modules/mod_headers.so
#LoadModule ident_module modules/mod_ident.so
#LoadModule imagemap_module modules/mod_imagemap.so
LoadModule include_module modules/mod_include.so
#LoadModule info_module modules/mod_info.so
LoadModule isapi_module modules/mod_isapi.so
#LoadModule ldap_module modules/mod_ldap.so
#LoadModule logio_module modules/mod_logio.so
LoadModule log_config_module modules/mod_log_config.so
#LoadModule log_forensic_module modules/mod_log_forensic.so
#LoadModule mem_cache_module modules/mod_mem_cache.so
LoadModule mime_module modules/mod_mime.so
#LoadModule mime_magic_module modules/mod_mime_magic.so
LoadModule negotiation_module modules/mod_negotiation.so
#LoadModule proxy_module modules/mod_proxy.so
#LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
#LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
#LoadModule proxy_connect_module modules/mod_proxy_connect.so
#LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
#LoadModule proxy_http_module modules/mod_proxy_http.so
#LoadModule proxy_scgi_module modules/mod_proxy_scgi.so
#LoadModule reqtimeout_module modules/mod_reqtimeout.so
#LoadModule rewrite_module modules/mod_rewrite.so
LoadModule setenvif_module modules/mod_setenvif.so
#LoadModule speling_module modules/mod_speling.so
#LoadModule ssl_module modules/mod_ssl.so
#LoadModule status_module modules/mod_status.so
#LoadModule substitute_module modules/mod_substitute.so
#LoadModule unique_id_module modules/mod_unique_id.so
#LoadModule userdir_module modules/mod_userdir.so
#LoadModule usertrack_module modules/mod_usertrack.so
#LoadModule version_module modules/mod_version.so
#LoadModule vhost_alias_module modules/mod_vhost_alias.so
LoadModule php5_module "c:/Program Files/php/php5apache2_2.dll"

<IfModule !mpm_netware_module>
<IfModule !mpm_winnt_module>
#
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.
#
# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
#
User daemon
Group daemon

</IfModule>
</IfModule>

# 'Main' server configuration
#
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition.  These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
#
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
#

#
# ServerAdmin: Your address, where problems with the server should be
# e-mailed.  This address appears on some server-generated pages, such
# as error documents.  e.g. admin@your-domain.com
#
ServerAdmin webmaster@somenet.com

#
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
#
# If your host doesn't have a registered DNS name, enter its IP address here.
#
#ServerName www.somenet.com:80

#
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
DocumentRoot "C:/Program Files (x86)/Apache Software Foundation/Apache2.2/htdocs"

#
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
#
# First, we configure the "default" to be a very restrictive set of
# features.
#
<Directory />
    Options FollowSymLinks
    AllowOverride None
    Order deny,allow
    Deny from all
</Directory>

#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#

#
# This should be changed to whatever you set DocumentRoot to.
#
<Directory "C:/Program Files (x86)/Apache Software Foundation/Apache2.2/htdocs">
    #
    # Possible values for the Options directive are "None", "All",
    # or any combination of:
    #   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
    #
    # Note that "MultiViews" must be named *explicitly* --- "Options All"
    # doesn't give it to you.
    #
    # The Options directive is both complicated and important.  Please see
    # http://httpd.apache.org/docs/2.2/mod/core.html#options
    # for more information.
    #
    Options Indexes FollowSymLinks

    #
    # AllowOverride controls what directives may be placed in .htaccess files.
    # It can be "All", "None", or any combination of the keywords:
    #   Options FileInfo AuthConfig Limit
    #
    AllowOverride None

    #
    # Controls who can get stuff from this server.
    #
    Order allow,deny
    Allow from all

</Directory>

#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
<IfModule dir_module>
    DirectoryIndex index.html index.php
</IfModule>

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<FilesMatch "^\.ht">
    Order allow,deny
    Deny from all
    Satisfy All
</FilesMatch>

#
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog "logs/error.log"

#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn

<IfModule log_config_module>
    #
    # The following directives define some format nicknames for use with
    # a CustomLog directive (see below).
    #
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
    LogFormat "%h %l %u %t \"%r\" %>s %b" common

    <IfModule logio_module>
      # You need to enable mod_logio.c to use %I and %O
      LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
    </IfModule>

    #
    # The location and format of the access logfile (Common Logfile Format).
    # If you do not define any access logfiles within a <VirtualHost>
    # container, they will be logged here.  Contrariwise, if you *do*
    # define per-<VirtualHost> access logfiles, transactions will be
    # logged therein and *not* in this file.
    #
    CustomLog "logs/access.log" common

    #
    # If you prefer a logfile with access, agent, and referer information
    # (Combined Logfile Format) you can use the following directive.
    #
    #CustomLog "logs/access.log" combined
</IfModule>

<IfModule alias_module>
    #
    # Redirect: Allows you to tell clients about documents that used to
    # exist in your server's namespace, but do not anymore. The client
    # will make a new request for the document at its new location.
    # Example:
    # Redirect permanent /foo http://www.somenet.com/bar

    #
    # Alias: Maps web paths into filesystem paths and is used to
    # access content that does not live under the DocumentRoot.
    # Example:
    # Alias /webpath /full/filesystem/path
    #
    # If you include a trailing / on /webpath then the server will
    # require it to be present in the URL.  You will also likely
    # need to provide a <Directory> section to allow access to
    # the filesystem path.

    #
    # ScriptAlias: This controls which directories contain server scripts.
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the target directory are treated as applications and
    # run by the server when requested rather than as documents sent to the
    # client.  The same rules about trailing "/" apply to ScriptAlias
    # directives as to Alias.
    #
    ScriptAlias /cgi-bin/ "C:/Program Files (x86)/Apache Software Foundation/Apache2.2/cgi-bin/"

</IfModule>

<IfModule cgid_module>
    #
    # ScriptSock: On threaded servers, designate the path to the UNIX
    # socket used to communicate with the CGI daemon of mod_cgid.
    #
    #Scriptsock logs/cgisock
</IfModule>

#
# "C:/Program Files (x86)/Apache Software Foundation/Apache2.2/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "C:/Program Files (x86)/Apache Software Foundation/Apache2.2/cgi-bin">
    AllowOverride None
    Options None
    Order allow,deny
    Allow from all
</Directory>

#
# DefaultType: the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value.  If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
#
DefaultType text/plain

<IfModule mime_module>
    #
    # TypesConfig points to the file containing the list of mappings from
    # filename extension to MIME-type.
    #
    TypesConfig conf/mime.types

    #
    # AddType allows you to add to or override the MIME configuration
    # file specified in TypesConfig for specific file types.
    #
    #AddType application/x-gzip .tgz
    #
    # AddEncoding allows you to have certain browsers uncompress
    # information on the fly. Note: Not all browsers support this.
    #
    #AddEncoding x-compress .Z
    #AddEncoding x-gzip .gz .tgz
    #
    # If the AddEncoding directives above are commented-out, then you
    # probably should define those extensions to indicate media types:
    #
    AddType application/x-compress .Z
    AddType application/x-gzip .gz .tgz

    #
    # AddHandler allows you to map certain file extensions to "handlers":
    # actions unrelated to filetype. These can be either built into the server
    # or added with the Action directive (see below)
    #
    # To use CGI scripts outside of ScriptAliased directories:
    # (You will also need to add "ExecCGI" to the "Options" directive.)
    #
    #AddHandler cgi-script .cgi

    # For type maps (negotiated resources):
    #AddHandler type-map var

    #
    # Filters allow you to process content before it is sent to the client.
    #
    # To parse .shtml files for server-side includes (SSI):
    # (You will also need to add "Includes" to the "Options" directive.)
    #
    #AddType text/html .shtml
    #AddOutputFilter INCLUDES .shtml

    AddType application/x-httpd-php .php
</IfModule>

#
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type.  The MIMEMagicFile
# directive tells the module where the hint definitions are located.
#
#MIMEMagicFile conf/magic

#
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
#
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.somenet.com/subscription_info.html
#

#
# MaxRanges: Maximum number of Ranges in a request before
# returning the entire resource, or one of the special
# values 'default', 'none' or 'unlimited'.
# Default setting is to accept 200 Ranges.
#MaxRanges unlimited

#
# EnableMMAP and EnableSendfile: On systems that support it,
# memory-mapping or the sendfile syscall is used to deliver
# files.  This usually improves server performance, but must
# be turned off when serving from networked-mounted
# filesystems or if support for these functions is otherwise
# broken on your system.
#
#EnableMMAP off
#EnableSendfile off

# Supplemental configuration
#
# The configuration files in the conf/extra/ directory can be
# included to add extra features or to modify the default configuration of
# the server, or you may simply copy their contents here and change as
# necessary.

# Server-pool management (MPM specific)
#Include conf/extra/httpd-mpm.conf

# Multi-language error messages
#Include conf/extra/httpd-multilang-errordoc.conf

# Fancy directory listings
#Include conf/extra/httpd-autoindex.conf

# Language settings
#Include conf/extra/httpd-languages.conf

# User home directories
#Include conf/extra/httpd-userdir.conf

# Real-time info on requests and configuration
#Include conf/extra/httpd-info.conf

# Virtual hosts
#Include conf/extra/httpd-vhosts.conf

# Local access to the Apache HTTP Server Manual
#Include conf/extra/httpd-manual.conf

# Distributed authoring and versioning (WebDAV)
#Include conf/extra/httpd-dav.conf

# Various default settings
#Include conf/extra/httpd-default.conf

# Secure (SSL/TLS) connections
#Include conf/extra/httpd-ssl.conf
#
# Note: The following must must be present to support
#       starting without SSL on platforms with no /dev/random equivalent
#       but a statically compiled-in mod_ssl.
#
<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
</IfModule>

PHPIniDir "c:/Program Files/php"

그리고 vhosts.conf :

NameVirtualHost 127.0.0.1:80

<VirtualHost 127.0.0.1:80>
    DocumentRoot i:/projects/webserver/__tools/phpmyadmin/
    ServerName dbadmin.tools
</VirtualHost>



답변

2016 년 10 월 업데이트

4 년 전,이 답변은 많은 사람들이 참조로 사용했기 때문에이 기간 동안 보안 관점에서 많은 것을 배웠지 만 중요한 메모를 명확히 할 책임이 있으며 그에 따라 답변을 업데이트했습니다.

원래 답변은 정확하지만 일부 프로덕션 환경에서는 안전하지 않으며 환경을 설정하는 동안 발생할 수있는 몇 가지 문제에 대해 설명하고 싶습니다.

빠른 솔루션을 찾고 있고 보안이 중요하지 않은 경우 (예 : 개발 환경) 대신 원래 답변을 건너 뛰고 읽으십시오.

많은 시나리오가 403 금지로 이어질 수 있습니다 .


A. 디렉토리 인덱스 (에서 mod_autoindex.c)

당신이 디렉토리에 액세스하고이 디렉토리에 디폴트 파일이없는 경우
아파치는 Options Indexes이 디렉토리를 사용할 수 없습니다.

A.1. DirectoryIndex옵션 예

DirectoryIndex index.html default.php welcome.php

A.2. Options Indexes선택권

설정된 경우, 기본 파일을 찾지 못한 경우 Apache는 디렉토리 내용을 나열합니다 (위의 ?? 옵션에서).

위의 조건 중 어느 것도 만족되지 않으면

403 Forbidden 을 받게됩니다

추천

  • REALLY가 필요 하지 않으면 디렉토리 목록을 허용하지 않아야 합니다.
  • 기본 색인 DirectoryIndex을 최소로 제한하십시오 .
  • 수정하려는 경우, 예, 사용을 위해, 오직 필요한 디렉토리에 수정을 제한하는 .htaccess파일 또는 내부에 수정을 넣어 <Directory /my/directory>지침

B. deny,allow지시어 (Apache 2.2)


귀하가 요청한 의견에 @Radu, @Simon A. Eugster가 언급 한 사항 은 해당 지침에 의해 거부, 블랙리스트 또는 화이트리스트입니다.

나는 완전한 설명을 게시하지는 않겠지 만, 몇 가지 예가이 규칙을 간단히 이해하는 데 도움이 될 수 있다고 생각합니다.

둘 다 일치하는 경우, 마지막 지시문은 승리 할 것입니다

Order allow,deny

두 지시어와 일치하면 거부됩니다 ( conf에서 allow지시어가 작성된 후에도 deny)

Order deny,allow

두 지시어와 일치하면 allow가 승리합니다.

실시 예 1

Order allow,deny
Allow from localhost mydomain.com

localhost와 * .mydomain.com만이 이것에 액세스 할 수 있으며 다른 모든 호스트는 거부됩니다

실시 예 2

Order allow,deny
Deny from evil.com
Allow from safe.evil.com # <-- has no effect since this will be evaluated first

모든 요청이 거부되고 마지막 줄이 당신을 속일 수도 있지만 마지막 승리 규칙 (여기서 거부는 마지막)과 일치하는 경우 서면과 동일하다는 것을 기억하십시오.

Order allow,deny
Allow from safe.evil.com
Deny from evil.com # <-- will override the previous one

실시 예 4

Order deny,allow
Allow from site.com
Deny from untrusted.site.com # <-- has no effect since this will be matched by the above `Allow` directive

모든 호스트의 요청이 수락됩니다

예 4 : 공개 사이트에 일반적인 경우 (블랙리스트에 올리지 않는 한 허용)

Order allow,deny
Allow from all
Deny from hacker1.com
Deny from hacker2.com

예 5 : 인트라넷 및 보안 사이트에 일반적인 경우 (허용되지 않은 경우 거부)

Order deny,allow
Deny from all
Allow from mypc.localdomain
Allow from managment.localdomain

C. Require지시문 (Apache 2.4)

Apache 2.4는 새로운 모듈을 사용합니다 mod_authz_host

Require all granted => 모든 요청 허용

Require all denied => 모든 요청 거부

Require host safe.com => safe.com에서만 허용


D. 파일 권한

대부분의 사람들이 잘못한 것은 파일 권한을 구성하는 것입니다.

황금률은

허가없이 시작하고 필요에 따라 추가

리눅스에서 :

  • 디렉토리는 Execute허가를 받아야한다

  • 파일에는 Read권한 이 있어야합니다

  • 예, 당신은 옳 Execute습니다 파일에 대한 권한을 추가하지 마십시오

예를 들어이 스크립트를 사용하여 폴더 권한을 설정합니다.

# setting permissions for /var/www/mysite.com

# read permission ONLY for the owner
chmod -R /var/www/mysite.com 400

# add execute for folders only
find /var/www/mysite.com -type d -exec chmod -R u+x {} \;

# allow file uploads
chmod -R /var/www/mysite.com/public/uploads u+w

# allow log writing to this folder
chmod -R /var/www/mysite.com/logs/

이 코드를 예로 게시했는데 다른 상황에서는 설정이 다를 수 있습니다



원래 답변

나는 같은 문제에 직면했지만 httpd.conf 의 전역 디렉토리 설정 또는 httpd-vhosts.conf 의 특정 디렉토리 블록에서 options 지시문 을 설정하여 해결했습니다 .

Options Indexes FollowSymLinks Includes ExecCGI

기본적으로 글로벌 디렉토리 설정은 (httpd.conf line ~188)다음과 같습니다.

<Directory />
    Options FollowSymLinks
    AllowOverride All
    Order deny,allow
    Allow from all
</Directory>

옵션을 다음으로 설정하십시오.
Options Indexes FollowSymLinks Includes ExecCGI

마지막으로 다음과 같아야합니다.

<Directory />
    #Options FollowSymLinks
    Options Indexes FollowSymLinks Includes ExecCGI
    AllowOverride All
    Order deny,allow
    Allow from all
</Directory>

또한 변경 시도 Order deny,allowAllow from all에 의해 선 Require all granted.

부록

디렉토리 색인 소스 코드 (일부 코드는 간결성을 위해 제거)

if (allow_opts & OPT_INDEXES) {
     return index_directory(r, d);
} else {
        const char *index_names = apr_table_get(r->notes, "dir-index-names");

        ap_log_rerror(APLOG_MARK, APLOG_ERR, 0, r, APLOGNO(01276)
                      "Cannot serve directory %s: No matching DirectoryIndex (%s) found, and "
                      "server-generated directory index forbidden by "
                      "Options directive",
                       r->filename,
                       index_names ? index_names : "none");
        return HTTP_FORBIDDEN;
    }


답변

이 문제가 해결되었음을 이해하지만 같은 문제를 저절로 해결했습니다.

의 원인

금지이 서버에 액세스 할 수있는 권한이 없습니다

실제로는 아파치 디렉토리의 기본 구성입니다 httpd.conf.

#
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
#
# First, we configure the "default" to be a very restrictive set of
# features.
#
<Directory "/">
    Options FollowSymLinks
    AllowOverride None
    Order deny,allow
    Deny from all          # the cause of permission denied
</Directory>

간단하게 변경 Deny from all하는 Allow from all권한 문제를 해결해야한다.

또는 더 나은 방법은 가상 호스트 구성에 대한 개별 디렉토리 권한을 지정하는 것입니다.

<VirtualHost *:80>
    ....

    # Set access permission
    <Directory "/path/to/docroot">
        Allow from all
    </Directory>

    ....
</VirtualHost>

현재 아파치 2.4 그러나, 액세스 제어는 새로운 모듈을 사용하여 수행된다 mod_authz_host( 2.2에서 2.4로 업그레이드 ). 따라서 새로운 Require지시문을 사용해야합니다.

<VirtualHost *:80>
    ....

    # Set access permission
    <Directory "/path/to/docroot">
        Require all granted
    </Directory>

    ....
</VirtualHost>


답변

기본 / var / www / 외부에서 호스팅되는 디렉토리의 일반적인 문제점은 Apache 사용자에게 사이트가 호스팅되는 디렉토리 및 하위 디렉토리에 대한 권한 만 필요하지 않다는 것입니다. Apache는 사이트가 호스팅되는 파일 시스템의 루트까지 모든 디렉토리에 대한 권한을 요구합니다. Apache는 설치시 / var / www /에 할당 된 권한을 자동으로 가져옵니다. 따라서 호스트 디렉토리가 바로 그 아래에있는 경우에는 적용되지 않습니다. 편집 : Daybreaker는 자신의 Apache가 기본 디렉토리에 대한 올바른 액세스 권한없이 설치되었다고보고했습니다.

예를 들어 개발 머신이 있고 사이트의 디렉토리는 다음과 같습니다.

/username/home/Dropbox/myamazingsite/

다음과 같이 도망 갈 수 있다고 생각할 수도 있습니다.

chgrp -R www-data /username/home/Dropbox/myamazingsite/
chmod -R 2750 /username/home/Dropbox/myamazingsite/

Apache가 사이트의 디렉토리에 액세스 할 수있는 권한을 부여하기 때문입니까? 글쎄 맞지만 충분하지 않습니다. Apache는 디렉토리 트리까지 모든 권한을 요구하므로 다음과 같이해야합니다.

chgrp -R www-data /username/
chmod -R 2750 /username/

분명히 나는 ​​디렉토리 구조의 내용을 분석하지 않고 프로덕션 서버의 Apache에 완전한 디렉토리 구조에 대한 액세스 권한을 부여하지 않는 것이 좋습니다. 프로덕션 환경에서는 기본 디렉토리 또는 웹 자산을 보관하기위한 다른 디렉토리 구조를 유지하는 것이 가장 좋습니다.

Edit2 : u / chimeraha가 지적했듯이 권한으로 수행중인 작업이 확실하지 않으면 홈 디렉토리에서 사이트를 잠그지 않도록 사이트 디렉토리를 홈 디렉토리 밖으로 옮기는 것이 가장 좋습니다.


답변

Apache 2.4에서 일부 구성 매개 변수가 변경되었습니다. Zend Framework 2 응용 프로그램을 설정할 때 비슷한 문제가 발생했습니다 . 몇 가지 조사 후 해결책은 다음과 같습니다.

잘못된 구성

<VirtualHost *:80>
    ServerName zf2-tutorial.localhost
    DocumentRoot /path/to/zf2-tutorial/public
    SetEnv APPLICATION_ENV "development"
    <Directory /path/to/zf2-tutorial/public>
        DirectoryIndex index.php
        AllowOverride All
        Order allow,deny #<-- 2.2 config
        Allow from all #<-- 2.2 config
    </Directory>
</VirtualHost>

올바른 구성

<VirtualHost *:80>
    ServerName zf2-tutorial.localhost
    DocumentRoot /path/to/zf2-tutorial/public
    SetEnv APPLICATION_ENV "development"
    <Directory /path/to/zf2-tutorial/public>
        DirectoryIndex index.php
        AllowOverride All
        Require all granted #<-- 2.4 New configuration
    </Directory>
</VirtualHost>

Apache 2.2에서 2.4로 마이그레이션하려는 경우 다음을 참조하십시오. http://httpd.apache.org/docs/2.4/upgrading.html


답변

아파치 2.2

Order Deny,Allow
Allow from all

아파치 2.4

Require all granted

에서 http://httpd.apache.org/docs/2.4/en/upgrading.html


답변

우분투 14.04 사용하여 아파치 2.4 , I는 다음했다 :

apache2.conf 파일 (아래에 있음 /etc/apache2)에 다음을 추가하십시오 .

<Directory /home/rocky/code/documentroot/>
  Options Indexes FollowSymLinks
  AllowOverride None
  Require all granted
</Directory>

서버를 다시로드하십시오.

sudo service apache2 reload

편집 : 이것은 Apache 2.4가있는 OS X Yosemite에서도 작동합니다. 가장 중요한 라인은

모든 권한 부여 필요


답변

WAMP 서버를 사용하는 경우 다음을 시도하십시오.

  • 작업 표시 줄에서 WAMP 서버 아이콘을 한 번 클릭

  • 온라인 옵션을 선택하십시오

  • 서버가 자동으로 다시 시작됩니다

  • 그런 다음 로컬 웹 사이트에 액세스하십시오