Aller au contenu

Activer Function Mail Et Cgi Sur Ds207+ ?


yves42

Messages recommandés

:fool: Qqun peut me dire comment activer les commandes function mail et les CGI pour les script dans un DS 207+ et si possible installer ipkg?

Merci Beaucoup

Bonjour,

Tu trouveras ton bonheur ici pour l'installation d'IPKG :good:

CGI je sais pas :vava:

Tu cherches la fonction mail sous PHP ? :unknw:

Lien vers le commentaire
Partager sur d’autres sites

Va voir sur le site de Fred : Serveur de Mail POP et SMTP sur un SYNO

Salut,

Merci pour tes réponses trés rapide j'ai beaucoup appris en peut de temps avec tes réponses et les tutos que tu m'a indiqués. :hi: Mais j'ai toujours les mêmes problémes lors de l'envoie de mail sur un script en php l'ai le message d'erreur suivant :

ERROR PHP [warning]: 'mail() [

function.mail]: Failed to send mail. (Failed to resolve host address.)'.

Je ni comprend rien...

Quand a l'utilisation des CGI avec perl j'ai aucune réponse mais j'ai vu dans http://ipkg.nslu2-linux.org/feeds/optware/...cross/unstable/ des tas de module en .ipk qui commence par perl*.ipk mais je ne sait pas lequel utiliser pour activer CGI perl???

:vava:

P.S. tu peux regarder la configuration de php ici http://www.yvesebizet.com/test.php

Lien vers le commentaire
Partager sur d’autres sites

Bonjour,

Fais moi suivre ton script PHP qui te donne cette erreur dans mon formulaire ici :

ERROR PHP [warning]: 'mail() [function.mail]: Failed to send mail. (Failed to resolve host address.)'.

Bonjour,

Pour information j'ai toujours pas reçu ton script PHP !

Lien vers le commentaire
Partager sur d’autres sites

Bonjour,

Pour information j'ai toujours pas reçu ton script PHP !

Bonjour,

Je suis nouveau dans ce forum et pour tout dire nul en apache. Je viens d'acquérir un serveur Synology DS 207+ Il est sur une base Apache 2.0 et PHP 5.2.0.

J'essaye desesperement de modifier httpd.conf et httpd.conf-user mais rien ne se passe!!! :evil:

Je vous mets ci-dessous mes 2 fichiers, si quelque un pouvait m'indiquer les modifications a éffectués pour que mon serveur puisse executer les CGI.

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"]URL:http://httpd.apache.org/docs/2.2[/url]> for detailed information.

# In particular, see 

# <[url="http://httpd.apache.org/docs/2.2/mod/directives.html"]URL:http://httpd.apache.org/docs/2.2/mod/directives.html[/url]>

# 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 "@@ServerRoot@@" will be interpreted by the

# server as "@@ServerRoot@@/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/syno/apache"


#

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

Listen 


#

# 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 ssl_module modules/mod_ssl.so

LoadModule rewrite_module modules/mod_rewrite.so

LoadModule cgi-module modules/mod_cgi.so

LoadModule alias_module/mod_alias.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 admin

Group users

</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. [email="admin@your-domain.com"]admin@your-domain.com[/email]

#

ServerAdmin admin


#

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


#

# 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/services/web"


#

# 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 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 "/var/services/web">

	#

	# 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

	# [url="http://httpd.apache.org/docs/2.2/mod/core.html#options"]http://httpd.apache.org/docs/2.2/mod/core.html#options[/url]

	# for more information.

	#

	Options MultiViews


	#

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


	#

	# 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.htm index.cgi index.php index.php3

</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 /var/log/httpd-user.log

ErrorLog /dev/null


#

# LogLevel: Control the number of messages logged to the error_log.

# Possible values include: debug, info, notice, warn, error, crit,

# alert, emerg.

#

#LogLevel debug

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 /dev/null 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 [url="http://www.example.com/bar"]http://www.example.com/bar[/url]


	#

	# 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/syno/apache/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/syno/apache/cgi-bin"

# should be changed to whatever your ScriptAliased

# CGI directory exists, if you have that configured.

#

<Directory "/usr/syno/apache/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 /usr/syno/apache/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 image/x-icon .ico

</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 /usr/syno/apache/conf/magic


#

# Customizable error responses come in three flavors:

# 1) plain text 2) local redirects 3) external redirects

#

# Some examples:

# Forbidden (eg. list files in a directory)

ErrorDocument 403 /webdefault/sample.php?status=403

# Page not found in apache

ErrorDocument 404 /webdefault/sample.php?status=404

# Page not found in thttpd

ErrorDocument 500 /webdefault/sample.php?status=500

#ErrorDocument 500 "The server made a boo boo."

#ErrorDocument 404 /missing.html

#ErrorDocument 404 "/cgi-bin/missing_handler.pl"

#ErrorDocument 402 [url="http://www.example.com/subscription_info.html"]http://www.example.com/subscription_info.html[/url]

#


#

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


# Multi-language error messages

#Include conf/extra/httpd-multilang-errordoc.conf


# Fancy directory listings

Include conf/extra/httpd-autoindex.conf-user


# Language settings

Include conf/extra/httpd-languages.conf-user


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


<IfDefine SSL>

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

</IfDefine>


AddType application/x-httpd-php .php

LoadModule php5_module /lib/libphp5.so

DocumentRoot "/var/services/web"
HTTPD.CONF-USER
#

# 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"]URL:http://httpd.apache.org/docs/2.2[/url]> for detailed information.

# In particular, see 

# <[url="http://httpd.apache.org/docs/2.2/mod/directives.html"]URL:http://httpd.apache.org/docs/2.2/mod/directives.html[/url]>

# 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 "@@ServerRoot@@" will be interpreted by the

# server as "@@ServerRoot@@/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/syno/apache"


#

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

Listen 


#

# 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 ssl_module modules/mod_ssl.so

LoadModule rewrite_module modules/mod_rewrite.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 admin

Group users

</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. [email="admin@your-domain.com"]admin@your-domain.com[/email]

#

ServerAdmin admin


#

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


#

# 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/services/web"


#

# 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 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 "/var/services/web">

	#

	# 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

	# [url="http://httpd.apache.org/docs/2.2/mod/core.html#options"]http://httpd.apache.org/docs/2.2/mod/core.html#options[/url]

	# for more information.

	#

	Options MultiViews


	#

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


	#

	# 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.htm index.cgi index.php index.php3

</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 /var/log/httpd-user.log

ErrorLog /dev/null


#

# LogLevel: Control the number of messages logged to the error_log.

# Possible values include: debug, info, notice, warn, error, crit,

# alert, emerg.

#

#LogLevel debug

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 /dev/null 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 [url="http://www.example.com/bar"]http://www.example.com/bar[/url]


	#

	# 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/syno/apache/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/syno/apache/cgi-bin" should be changed to whatever your ScriptAliased

# CGI directory exists, if you have that configured.

#

#<Directory "/usr/syno/apache/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 /usr/syno/apache/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 image/x-icon .ico

</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 /usr/syno/apache/conf/magic


#

# Customizable error responses come in three flavors:

# 1) plain text 2) local redirects 3) external redirects

#

# Some examples:

# Forbidden (eg. list files in a directory)

ErrorDocument 403 /webdefault/sample.php?status=403

# Page not found in apache

ErrorDocument 404 /webdefault/sample.php?status=404

# Page not found in thttpd

ErrorDocument 500 /webdefault/sample.php?status=500

#ErrorDocument 500 "The server made a boo boo."

#ErrorDocument 404 /missing.html

#ErrorDocument 404 "/cgi-bin/missing_handler.pl"

#ErrorDocument 402 [url="http://www.example.com/subscription_info.html"]http://www.example.com/subscription_info.html[/url]

#


#

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


# Multi-language error messages

#Include conf/extra/httpd-multilang-errordoc.conf


# Fancy directory listings

Include conf/extra/httpd-autoindex.conf-user


# Language settings

Include conf/extra/httpd-languages.conf-user


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


<IfDefine SSL>

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

</IfDefine>


AddType application/x-httpd-php .php

LoadModule php5_module /lib/libphp5.so
HTTPD.CONF-SYS
#

# 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"]URL:http://httpd.apache.org/docs/2.2[/url]> for detailed information.

# In particular, see 

# <[url="http://httpd.apache.org/docs/2.2/mod/directives.html"]URL:http://httpd.apache.org/docs/2.2/mod/directives.html[/url]>

# 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 "@@ServerRoot@@" will be interpreted by the

# server as "@@ServerRoot@@/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/syno/apache"


#

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

Listen 5000


#

# 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 ssl_module modules/mod_ssl.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 root

Group root

</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. [email="admin@your-domain.com"]admin@your-domain.com[/email]

#

ServerAdmin admin


#

# 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 *:5000


#

# 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 "/usr/syno/synoman"


#

# 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 ExecCGI FollowSymLinks MultiViews

	AllowOverride 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/syno/synoman">

	#

	# 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

	# [url="http://httpd.apache.org/docs/2.2/mod/core.html#options"]http://httpd.apache.org/docs/2.2/mod/core.html#options[/url]

	# for more information.

	#

	Options ExecCGI FollowSymLinks MultiViews


	#

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


	#

	# 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.htm index.cgi

</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 /var/log/httpd-sys.log

ErrorLog /dev/null


#

# LogLevel: Control the number of messages logged to the error_log.

# Possible values include: debug, info, notice, warn, error, crit,

# alert, emerg.

#

LogLevel debug


<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 /dev/null common


	#

	# If you prefer a logfile with access, agent, and referer information

	# (Combined Logfile Format) you can use the following directive.

	#

	#CustomLog /usr/syno/apache/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 [url="http://www.example.com/bar"]http://www.example.com/bar[/url]


	#

	# 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/syno/apache/cgi-bin/"


	#

	# Synology Web File Manager

	# For UTF-8 filename download issue on Safari, we embedded UTF-8 filename on URL.

	# All URL prefixed "/webfm/cgi/download" should be redirect to CGI of web file manager's download.

	#

	AliasMatch ^/webfm/cgi/download/(.*)/.+ "/usr/syno/synoman/webfm/cgi/$1"

</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/syno/apache/cgi-bin"

 #should be changed to whatever your ScriptAliased

# CGI directory exists, if you have that configured.

#

<Directory "/usr/syno/apache/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 /usr/syno/apache/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

	AddType image/x-icon .ico


	#

	# 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 /usr/syno/apache/conf/magic


#

# Customizable error responses come in three flavors:

# 1) plain text 2) local redirects 3) external redirects

#

# Some examples:

ErrorDocument 500 /error.cgi?status=500

ErrorDocument 404 /error.cgi?status=404

ErrorDocument 403 /error.cgi?status=403

#ErrorDocument 402 [url="http://www.example.com/subscription_info.html"]http://www.example.com/subscription_info.html[/url]

#


#

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


# Multi-language error messages

#Include conf/extra/httpd-multilang-errordoc.conf


# Fancy directory listings

Include conf/extra/httpd-autoindex.conf-sys


# Language settings

Include conf/extra/httpd-languages.conf-sys


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


<IfDefine SSL>

# Secure (SSL/TLS) connections

Include conf/extra/httpd-ssl.conf-sys

#

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

</IfDefine>

:D Merci de vos réponse (détaillée pour un novice)

Lien vers le commentaire
Partager sur d’autres sites

Bonjour,

Avez-vous réussi finalement à faire fonctionner les CGI ?

Je piétine pour ma part.

J'ai cru comprendre qu'IPKQ installe Perl automatiquement, mais que IPKG n'est pas encore installable sur un 207+ faute de processeur.

=> Il faut donc l'installer manuellement. Quelqu'un a-t-il réussi ?

De plus certains fichiers de l'admin Synology sont en .cgi : cela veut-il dire que Perl est déjà installé quelque part ??? Je n'arrive pas à ouvrir ces fichiers pour trouver l'adresse de l'éventuel interpréteur.

Merci d'avance pour votre aide :yahoo:

Lien vers le commentaire
Partager sur d’autres sites

Bonjour,

Avez-vous réussi finalement à faire fonctionner les CGI ?

Je piétine pour ma part.

J'ai cru comprendre qu'IPKQ installe Perl automatiquement, mais que IPKG n'est pas encore installable sur un 207+ faute de processeur.

=> Il faut donc l'installer manuellement. Quelqu'un a-t-il réussi ?

De plus certains fichiers de l'admin Synology sont en .cgi : cela veut-il dire que Perl est déjà installé quelque part ??? Je n'arrive pas à ouvrir ces fichiers pour trouver l'adresse de l'éventuel interpréteur.

Merci d'avance pour votre aide :yahoo:

Bonsoir,

Ah si sur un 207+ le bootstrap et 900 package sont disponibles

Regarde un peu ici : http://www.nas-forum.com/forum/index.php?showforum=72 sur les 2 premiers sujets...De mémoire il faut juste modifier le fichier config d'ipkg pour qu'il aille chercher les packages compatibles.

Lien vers le commentaire
Partager sur d’autres sites

Ah ok super merci, je n'avais pas vu.

Mais déjà que j'ai eu du mal à comprendre ce qu'est ipkg, maintenant ça parle de "bootstrap", je suis perdu ! C'est du chinois tout ça, mais bon je vais essayer.

Installer ipkg juste pouvoir perl, c'est censé ou pas ? (autrement je m'en fiche d'ipkg, je n'en aurai pas l'usage).

Merci en tout cas.

Lien vers le commentaire
Partager sur d’autres sites

Ah ok super merci, je n'avais pas vu.

Mais déjà que j'ai eu du mal à comprendre ce qu'est ipkg, maintenant ça parle de "bootstrap", je suis perdu ! C'est du chinois tout ça, mais bon je vais essayer.

Installer ipkg juste pouvoir perl, c'est censé ou pas ? (autrement je m'en fiche d'ipkg, je n'en aurai pas l'usage).

Merci en tout cas.

Bonjour,

Installer ipkg pour installer perl n'est pas incensé du tous loin de la ;)

Et pour le bootstrap ca permet en fait d'installer des choses sur un syno en utisant le disque dur comme 'extension du systeme' car ce dernier , tu doit t'en douter, n'est pas extensible en terme de place a l'infini :) .

Lien vers le commentaire
Partager sur d’autres sites

bonjours,

j'ai installer 'xmail' (sans le php) et il répond 100% par telnet 192.168.1.15 25 & 192.168.1.15 110

l'ip de mon syno mais ou sont les paramêtres car un login avec un nom user existant est refusé !!

j'ai utiliser XMCrypt mais cela ne semble pas être la bonne carburation...

connexion acceptée mais login ou m-d-p refusé ??

une idée? - merçi

Lien vers le commentaire
Partager sur d’autres sites

bonjours,

j'ai installer 'xmail' (sans le php) et il répond 100% par telnet 192.168.1.15 25 & 192.168.1.15 110

l'ip de mon syno mais ou sont les paramêtres car un login avec un nom user existant est refusé !!

j'ai utiliser XMCrypt mais cela ne semble pas être la bonne carburation...

connexion acceptée mais login ou m-d-p refusé ??

une idée? - merçi

Bonjours,

Je presume que tu as utilisé ce tuto ici : http://fredo.servehttp.com/html/Astu-11.htm

Donc modifié le fichier ctrlaccount.tab avec la tabulation entre admin et le mdp crypté ?

Je te preconise l'installation de phpxmail car pour la gestion c'est largement mieux !!!

Personnelement j ai suivi le tuto de fred a la lettre et RAS tous a bien fonctionné.

Lien vers le commentaire
Partager sur d’autres sites

Archivé

Ce sujet est désormais archivé et ne peut plus recevoir de nouvelles réponses.

×
×
  • Créer...

Information importante

Nous avons placé des cookies sur votre appareil pour aider à améliorer ce site. Vous pouvez choisir d’ajuster vos paramètres de cookie, sinon nous supposerons que vous êtes d’accord pour continuer.