J'ai réussi grace à ce tuto: [articlebin.michaelmilette.com] à faire fonctionner https avec Wamp. Seulement il me reste un problème, j'ai créé un VirtualHost mais lorsque je l'appelle en https, il me renvoi vers la page d'accueil de Wamp. En fait, il me renvoie vers DocumentRoot que j'ai indiqué dans <VirtualHost _default_:443> du fichier httpd-ssl.conf
Désolé, mais je ne suis pas du tout familier avec toutes ces configurations.
Est ce que quelqu'un aurait la solution à ce problème, ou alors un tuto complet pour faire fonctionner https avec Wamp 3.
---------------------------------------------------------------------------------------------------------------------------------------------------------------- Mon site : [www.jcz.fr]
[ code ] # # This is the main Apache HTTP server configuration file. It contains the # configuration directives that give the server its instructions. # See <URL:[httpd.apache.org]; for detailed information. # In particular, see # <URL:[httpd.apache.org]; # 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/access_log" # with ServerRoot set to "/usr/local/apache2" will be interpreted by the # server as "/usr/local/apache2/logs/access_log", whereas "/logs/access_log" # will be interpreted as '/logs/access_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. ServerSignature On ServerTokens Full
# # 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 specify a local disk on the # Mutex directive, if file-based mutexes are used. If you wish to share the # same ServerRoot for multiple httpd daemons, you will need to change at # least PidFile. # # Apache variable names used by Apache conf files: # The names and contents of variables: # APACHE24, VERSION_APACHE, INSTALL_DIR, APACHE_DIR # should never be changed. Define APACHE24 Apache2.4 Define VERSION_APACHE 2.4.33 Define INSTALL_DIR d:/wamp64 Define APACHE_DIR ${INSTALL_DIR}/bin/apache/apache${VERSION_APACHE} Define MYPORT8082 8082 Define MYPORT8081 8081
ServerRoot "${APACHE_DIR}" # # Mutex: Allows you to set the mutex mechanism and mutex file directory # for individual mutexes, or change the global defaults # # Uncomment and change the directory if mutexes are file-based and the default # mutex file directory is not on a local disk or is not appropriate for some # other reason. # # Mutex default:logs
# # 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 0.0.0.0:80 Listen [::0]:80 Listen 0.0.0.0:${MYPORT8082} Listen [::0]:${MYPORT8082} Listen 0.0.0.0:${MYPORT8081} Listen [::0]:${MYPORT8081}
<IfModule unixd_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>
# '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 wampserver@wampserver.invalid
# # 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 localhost:80
# # Deny access to the entirety of your server's filesystem. You must # explicitly permit access to web content directories in other # <Directory> blocks below. # <Directory /> AllowOverride none Require all denied </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. # HostnameLookups Off
# # 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 "${INSTALL_DIR}/www" <Directory "${INSTALL_DIR}/www/"> # # 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 # [httpd.apache.org] # for more information. # Options +Indexes +FollowSymLinks +Multiviews
# # AllowOverride controls what directives may be placed in .htaccess files. # It can be "All", "None", or any combination of the keywords: # AllowOverride FileInfo AuthConfig Limit # AllowOverride all
# # Controls who can get stuff from this server. # # onlineoffline tag - don't remove Require all granted </Directory>
# # DirectoryIndex: sets the file that Apache will serve if a directory # is requested. # <IfModule dir_module> DirectoryIndex index.php index.php3 index.html index.htm </IfModule>
# # The following lines prevent .htaccess and .htpasswd files from being # viewed by Web clients. # <Files ".ht*"> Require all denied </Files>
# # 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" ErrorLog "${INSTALL_DIR}/logs/apache_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 "${INSTALL_DIR}/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 [www.example.com]
# # 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/ "${INSTALL_DIR}/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 cgisock </IfModule>
# # "c:/Apache24/cgi-bin" should be changed to whatever your ScriptAliased # CGI directory exists, if you have that configured. # <Directory "${INSTALL_DIR}/cgi-bin"> AllowOverride None Options None Require all granted </Directory>
<IfModule headers_module> # # Avoid passing HTTP_PROXY environment to CGI's on this or any proxied # backend servers which have lingering "httpoxy" defects. # 'Proxy' request header is undefined by the IETF, not listed by IANA # RequestHeader unset Proxy early </IfModule>
<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 AddType application/x-httpd-php .php AddType application/x-httpd-php .php3
# # 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 [www.example.com] #
# # 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 may be 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. # Defaults: EnableMMAP On, EnableSendfile Off # #EnableMMAP off EnableSendfile off
# AcceptFilter: On Windows, none uses accept() rather than AcceptEx() and # will not recycle sockets between connections. This is useful for network # adapters with broken driver support, as well as some virtual network # providers such as vpn drivers, or spam, virus or spyware filters. AcceptFilter http none AcceptFilter https none # 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.
# 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
# Configure mod_proxy_html to understand HTML4/XHTML1 <IfModule proxy_html_module> Include conf/extra/proxy-html.conf </IfModule>
# 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>
Include "${INSTALL_DIR}/alias/*"
[ /code ]
-------------------------------------- Et le fichier "httpd-vhosts.conf"
Je ne vois pas le virtualHost que vous utilisez avec le port 443 ?
Si vous désirez mettre en place le protocole https, vous devez activer le SSL dans WampServer. Or je n'ai rien vu de tel dans vos fichiers de configurations.
De plus, cela signifie que vous devez posséder un certificat SSL, même auto-signé, au moins pour faire des tests.
Je vous conseille de lire mon sujet sur les certificats SSL et la configuration de WampServer. --> [www.jcz.fr]
@+
---------------------------------------------------------------------------------------------------------------------------------------------------------------- Mon site : [www.jcz.fr]
Désolé, mais j'ai abandonné avec WampServer, à mon grand regret. J'y étais habitué, ca fonctionnait bien, j'étais vraiment très content. Mais mes 2 derniers problèmes: gestion du HTTPS et déplacement des dossiers www et datas n'ayant pas trouvé de solutions rapides et facile, j'ai essayé d'autres outils et au final j'ai trouvé AMPPS. J'aime moins, mais c'est sans doute une question d'habitude, mais mon problème de HTTPS est résolu ainsi que d'emplacement du dossier www. Pour le dossier Datas, ca été plus galère, mais j'ai réussi pas trouvé une solution.
J'espère que Wampserver s'améliorera prochainement et dans ce cas j'y reviendrai avec plaisir. Bon courage. Désolé de vous abandonner, mais j'ai trop besoin de ces fonctionnalités dans mon travail.
AMPPS utilise aussi Apache, MySql et Php. Vous aurez les mêmes problèmes qu'avec WampServer.
Je vous ai communiqué un lien pour configurer votre liaison en https. C'est-à-dire utiliser un certificats SSL pour sécuriser votre connexion à votre serveur apache.
Vous devez pour cela vous procurer un certificat payant ou gratuit, par exemple Let's Encrypt et ensuite configurer Apache afin de faire le lien avec votre certificat. Ce n'est pas quelque chose de facile et nécessite d'avoir des connaissances aussi bien avec Apache qu'avec le SSL.
Je doute fortement que AMPPS vous fournisse une assistance sur cet aspect du paramétrage d'Apache.
Pour déplacer un répertoire, vous pouvez le faire avec windows. Mais il ne faut pas oublier de corriger le chemin dans votre virtualHosts et de redémarrer ensuite WampServer. Cela prend environ 15 secondes pour le faire.
@+
---------------------------------------------------------------------------------------------------------------------------------------------------------------- Mon site : [www.jcz.fr]
Pour le HTTPS avec AMPPS, il y a juste une case à cocher lors de l'ajout d'un domaine et ca à fonctionner immédiatement...c'est peut être pas parfait (le navigateur me demande validation à chaque fois), mais au moins ca marche et ca me permet de travailler. J'ai essayé de suivre ton tuto, mais c'est trop compliqué pour moi, je n'ai pas le niveau technique (je suis développeur et pas ingénieur réseau).
Pour le changement d'emplacement, c'est pareil, lors de l'ajout d'un domaine, j'ai indiqué le chemin vers mon NAS et ca a marché !!! Reste à résoudre le problème du changement de localisation pour le dossier qui contient la base de données. J'ai trouvé des tutos qui explique qui faut utiliser des symlink. Mais je n'ai pas les droits admin sur mon PC. Je demanderai à mon ingénieur maintenance de régler ce problème.
Je suis vraiment désolé pour vous et pour moi de devoir changer. Mais cela fait plusieurs années que WampServer aurait du prendre en compte la problématique du HTTPS. Des que cela sera fait, je reviendrai me blottir dans vos bras ;-) Marco