Contenu | Rechercher | Menus

Annonce

Si vous avez des soucis pour rester connecté, déconnectez-vous puis reconnectez-vous depuis ce lien en cochant la case
Me connecter automatiquement lors de mes prochaines visites.

À propos de l'équipe du forum.

#1 Le 29/12/2006, à 11:41

titirock

[Résolu]Erreur 403 avec Apache 2.2.3/PHP 5.2.0

Bonjour à tous!
J'ai installé un serveur Apache auquel j'ai intégré PHP 5.2.0. Le fichier httpd.conf est bien configuré j'ai donc voulu placer mes fichiers dans /var/www. J'ai modifié la directive DocumentRoot. Seulement quand je fais http://127.0.0.0.1/infos.php dans un navigateur, le serveur me renvoie un erreur 403 et le fichier error.log m'indique ceci :

[Fri Dec 29 11:19:52 2006] [error] [client 127.0.0.1] client denied by server configuration: /var/www/infos.php

hmm

kevin@ubuntu-test:/var$ ls -l
total 52
drwxr-xr-x  2 root    root    4096 2006-12-29 09:01 backups
drwxr-xr-x 15 root    root    4096 2006-12-28 23:17 cache
drwxr-xr-x  2 root    root    4096 2006-12-23 13:26 crash
drwxr-xr-x  2 root    root    4096 2006-12-21 19:57 games
drwxr-xr-x 53 root    root    4096 2006-12-29 10:54 lib
drwxrwsr-x  2 root    staff   4096 2006-10-20 00:49 local
drwxrwxrwt  2 root    root      40 2006-12-29 09:54 lock
drwxr-xr-x 13 root    root    4096 2006-12-29 10:54 log
drwxrwsr-x  2 root    mail    4096 2006-10-25 16:03 mail
drwxr-xr-x  2 root    root    4096 2006-10-25 16:03 opt
drwxr-xr-x  8 root    root    4096 2006-12-20 19:34 packages
drwxr-xr-x 15 root    root     680 2006-12-29 11:06 run
drwxr-xr-x  6 root    root    4096 2006-12-23 11:07 spool
drwxrwxrwt  4 root    root    4096 2006-12-28 23:15 tmp
drwxr-xr-x  2 apache2 apache2 4096 2006-12-29 11:17 www

J'ai crée un compte et un groupe dédié à Apache2.  J'ai déjà essayé chmod -R 755 www, mais c'est toujours pareil...
Merci d'avance pour votre aide

Dernière modification par titirock (Le 29/12/2006, à 16:21)


Alice est née au pays des cauchemars,
Je voudrais juste la rassurer...
--------------------------------------
http://www.tuxalafenetre.net

Hors ligne

#2 Le 29/12/2006, à 11:52

tuxy

Re : [Résolu]Erreur 403 avec Apache 2.2.3/PHP 5.2.0

salut,

vérifie les directives d'accés de ton hôte virtuel (genre qu'il y ai pas un deny ou allow qui va pas  ).

sinon tu peux aussi poster ta conf, qu'on y regarde de plus prés .
Mais à mon avis si les droits sur les répertoires et que ton .php est bien exécutable, c'est ta conf qui va pas (le httpd.conf, d'ailleurs je trouve bizarre de configurer apache2.2 avec ce fichier, vu qu'a partir de apache2, on lui préfère apache2.conf et ses fichiers annexes)

[edit] par contre je sais pas si c'est une bonne idée la création d'un groupe apache2 vu que par défaut le proprio est root avec group root .

Dernière modification par tuxy (Le 29/12/2006, à 11:55)


Je sais que je ne sais rien. 

- Socrate -

Hors ligne

#3 Le 29/12/2006, à 12:23

titirock

Re : [Résolu]Erreur 403 avec Apache 2.2.3/PHP 5.2.0

Voilà mon 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 "/usr/local/apache2" will be interpreted by the
# server as "/usr/local/apache2/logs/foo.log".

#
# 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 "/usr/local/apache2"

#
# 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 80

#
# 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 mime_magic_module modules/mod_mime_magic.so
LoadModule info_module modules/mod_info.so
LoadModule vhost_alias_module modules/mod_vhost_alias.so
LoadModule rewrite_module modules/mod_rewrite.so
LoadModule php5_module        modules/libphp5.so

<IfModule !mpm_netware_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 apache2
Group apache2
</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 monemail@mondomaine.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.mondomaine.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 "/var/www"

#
# 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 "/usr/local/apache2/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 index.phtml default.php default.html default.phtml		
</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.example.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/ "/usr/local/apache2/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>

#
# "/usr/local/apache2/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "/usr/local/apache2/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
</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.example.com/subscription_info.html
#

#
# 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>

#Configuration de PHP
AddType application/x-httpd-php .php .phtml

Pour le groupe/user apache2 j'ai lu ça dans un livre qui explique comment mettre en place un serveur LAMP, où il est écrit que ce serai plus sécurisé d'affecter un compte dédié à apache.
J'ai installé apache et PHP à partir des sources.

Voilà mes options de compilation d'Apache :

#! /bin/sh
#
# Created by configure

"./configure" \
"--enable-so" \
"--enable-cgi" \
"--enable-speling" \
"--enable-alias" \
"--enable-userdir" \
"--enable-mods-shared=auth_anon info mime_magic rewrite vhost_alias" \
"$@"

et de PHP:

#! /bin/sh
#
# Created by configure

'./configure' \
'--with-apxs2=/usr/local/apache2/bin/apxs' \
'--with-mysql' \
'--with-mysqli' \
'--enable-magic-quotes' \
'--with-pdo-mysql' \
'--enable-embbeded-mysqli' \
'--enable-ftp' \
'--enable-sqlite-utf8' \
'--enable-exif' \
"$@"

Dernière modification par titirock (Le 29/12/2006, à 16:22)


Alice est née au pays des cauchemars,
Je voudrais juste la rassurer...
--------------------------------------
http://www.tuxalafenetre.net

Hors ligne

#4 Le 29/12/2006, à 13:09

dexinou

Re : [Résolu]Erreur 403 avec Apache 2.2.3/PHP 5.2.0

Les options de compilations sont bonne sinon il t'aurais mi une erreur.

Ce qui m'interpèle c'est ça:

<Directory />
    Options FollowSymLinks
    AllowOverride None
    Order deny,allow
    Deny from all
</Directory>

Essai de modifier par ceci:

<Directory /var/www>
    Options Indexes FollowSymLinks MultiViews
    AllowOverride All
    Order allow,deny
    Allow from all
</Directory>

Dernière modification par dexinou (Le 29/12/2006, à 16:43)


Ubuntu 9.10 64bits ext4 ® Core 2 Duo
Unix..... il y a moins bien mais c'est plus cher.
Si t'as pas compris la réponse, pose mieux ta question.
Tutoriaux Linux, apache, pure-ftpd, bind, mysql, qmail...

Hors ligne

#5 Le 29/12/2006, à 15:25

titirock

Re : [Résolu]Erreur 403 avec Apache 2.2.3/PHP 5.2.0

Merci beaucoup! ça fonctionne maitenant!
J'ai fais ça :

<Directory />
    Options FollowSymLinks
    AllowOverride None
    Order deny,allow
    Deny from all
</Directory>

<Directory /var/www>
    Options Indexes FollowSymLinks MultiViews
    AllowOverride All
    Order allow,deny
    Allow from all
</Directory>

Donc si j'ai bien compris il faut ajouter ces directives dès que l'on veut avoir accès aux fichiers étant dans un répertoire donné.

Merci encore! big_smile

Dernière modification par titirock (Le 29/12/2006, à 16:23)


Alice est née au pays des cauchemars,
Je voudrais juste la rassurer...
--------------------------------------
http://www.tuxalafenetre.net

Hors ligne

#6 Le 29/12/2006, à 15:59

dexinou

Re : [Résolu]Erreur 403 avec Apache 2.2.3/PHP 5.2.0

Normalement c'est fait par défaut mais par sécurité (apparemment) apache à été configurer comme ça lorsqu'on décide le compiler.
J'ai jamais vu ça ! neutral


Ubuntu 9.10 64bits ext4 ® Core 2 Duo
Unix..... il y a moins bien mais c'est plus cher.
Si t'as pas compris la réponse, pose mieux ta question.
Tutoriaux Linux, apache, pure-ftpd, bind, mysql, qmail...

Hors ligne

#7 Le 29/12/2006, à 16:07

michel2652

Re : [Résolu]Erreur 403 avec Apache 2.2.3/PHP 5.2.0

Bonjour,

Effectivement en installant en suivant le tuto lamp.bis de la doc, c'est différent.

Un petit Résolu dans le titre, merci.

A+

#8 Le 29/12/2006, à 16:41

dexinou

Re : [Résolu]Erreur 403 avec Apache 2.2.3/PHP 5.2.0

michel2652 a écrit :

Bonjour,

Effectivement en installant en suivant le tuto lamp.bis de la doc, c'est différent.

Un petit Résolu dans le titre, merci.

A+

C'est sûr que ça va tout seul avec lamp mais on a pas les options qu'on veut c'est pour ça qu'on préfère tout compiler et choisir tel ou tel fonctions qui sont nécessaires par exemple avec gd.
On a des petits soucis aussi mais ils ne sont pas insurmontables

Dernière modification par dexinou (Le 29/12/2006, à 16:44)


Ubuntu 9.10 64bits ext4 ® Core 2 Duo
Unix..... il y a moins bien mais c'est plus cher.
Si t'as pas compris la réponse, pose mieux ta question.
Tutoriaux Linux, apache, pure-ftpd, bind, mysql, qmail...

Hors ligne

#9 Le 20/12/2007, à 16:40

youssoufoued

Re : [Résolu]Erreur 403 avec Apache 2.2.3/PHP 5.2.0

Bonjour,

Je vis présentement les mêmes difficultés avec PHP5 suite à  une installation LAMP. Ci-dessous mon post:
http://forum.ubuntu-fr.org/viewtopic.php?id=175960

Merci d'avance ,


Culturellement,


Culturellement,

Hors ligne