Ubuntu-fr

GhostSpirit

mauvaise redirection https pour owncloud

bonjour,

j'ai crée 3 sites web en local
monsite1.fr (avec alias)
monsite1.fr/zm (sans alias)
moncloud.monsite1.fr (avec alias)

j'ai dans /var/www:

/www/html/index.html
/www/html/zm
/www/moncloud.monsite1.fr
/www/monsite.fr

si je tape https://monsite1.fr/zm : c'est ok

quand je tate http://moncloud.monsite.fr j'arrive bien sur le cloud
quand je tape monsite1.fr c'est ok

mais quand je tape https/moncloud.monsite.fr je tombe sur www/html/index.html

PS : inutile de cliquer sur les lien ils n'arrive pas chez moi
au fait comment empecher la creation de lien quand je donne un exemple de lien ????
idem avec 127.0.0.1
idem avec 127.0.1.1
idem avec https://127.0.1.1
idem avec https://127.0.0.1
idem avec 192.168.1.2/
idem avec https://192.168.1.2/
idem avec https://moncloud.monsite.fr

j'aimerais aller sur var/www/monsite1.fr  quand je tape https://moniste1.fr
et sur var/www/moncloud.monsite.fr quand je tape https://moncloud.monsite1.fr

Dernière modification par GhostSpirit (Le 01/07/2015, à 12:07)

---

Apprendre, comprendre, progresser, et apprendre aux autres, telle est ma devise
http://forum.ubuntu-fr.org/viewforum.php?id=171

bruno

Re : mauvaise redirection https pour owncloud

Bonjour,

Il faut donner la configuration de tes hôtes virtuels.

GhostSpirit

Re : mauvaise redirection https pour owncloud

bonjour bruno,

je ne suis pas sûr de ce que tu demandes !
mais voilà default-ssl.conf

<IfModule mod_ssl.c>
	<VirtualHost _default_:443>
		ServerAdmin webmaster@localhost

		DocumentRoot /var/www/html/

		# Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
		# error, crit, alert, emerg.
		# It is also possible to configure the loglevel for particular
		# modules, e.g.
		#LogLevel info ssl:warn

		ErrorLog ${APACHE_LOG_DIR}/error.log
		CustomLog ${APACHE_LOG_DIR}/access.log combined

		# For most configuration files from conf-available/, which are
		# enabled or disabled at a global level, it is possible to
		# include a line for only one particular virtual host. For example the
		# following line enables the CGI configuration for this host only
		# after it has been globally disabled with "a2disconf".
		#Include conf-available/serve-cgi-bin.conf

		#   SSL Engine Switch:
		#   Enable/Disable SSL for this virtual host.
		SSLEngine on

		#   A self-signed (snakeoil) certificate can be created by installing
		#   the ssl-cert package. See
		#   /usr/share/doc/apache2/README.Debian.gz for more info.
		#   If both key and certificate are stored in the same file, only the
		#   SSLCertificateFile directive is needed.
		SSLCertificateFile	/etc/ssl/certs/ssl-cert-snakeoil.pem
		SSLCertificateKeyFile /etc/ssl/private/ssl-cert-snakeoil.key

		#   Server Certificate Chain:
		#   Point SSLCertificateChainFile at a file containing the
		#   concatenation of PEM encoded CA certificates which form the
		#   certificate chain for the server certificate. Alternatively
		#   the referenced file can be the same as SSLCertificateFile
		#   when the CA certificates are directly appended to the server
		#   certificate for convinience.
		#SSLCertificateChainFile /etc/apache2/ssl.crt/server-ca.crt

		#   Certificate Authority (CA):
		#   Set the CA certificate verification path where to find CA
		#   certificates for client authentication or alternatively one
		#   huge file containing all of them (file must be PEM encoded)
		#   Note: Inside SSLCACertificatePath you need hash symlinks
		#		 to point to the certificate files. Use the provided
		#		 Makefile to update the hash symlinks after changes.
		#SSLCACertificatePath /etc/ssl/certs/
		#SSLCACertificateFile /etc/apache2/ssl.crt/ca-bundle.crt

		#   Certificate Revocation Lists (CRL):
		#   Set the CA revocation path where to find CA CRLs for client
		#   authentication or alternatively one huge file containing all
		#   of them (file must be PEM encoded)
		#   Note: Inside SSLCARevocationPath you need hash symlinks
		#		 to point to the certificate files. Use the provided
		#		 Makefile to update the hash symlinks after changes.
		#SSLCARevocationPath /etc/apache2/ssl.crl/
		#SSLCARevocationFile /etc/apache2/ssl.crl/ca-bundle.crl

		#   Client Authentication (Type):
		#   Client certificate verification type and depth.  Types are
		#   none, optional, require and optional_no_ca.  Depth is a
		#   number which specifies how deeply to verify the certificate
		#   issuer chain before deciding the certificate is not valid.
		#SSLVerifyClient require
		#SSLVerifyDepth  10

		#   SSL Engine Options:
		#   Set various options for the SSL engine.
		#   o FakeBasicAuth:
		#	 Translate the client X.509 into a Basic Authorisation.  This means that
		#	 the standard Auth/DBMAuth methods can be used for access control.  The
		#	 user name is the `one line' version of the client's X.509 certificate.
		#	 Note that no password is obtained from the user. Every entry in the user
		#	 file needs this password: `xxj31ZMTZzkVA'.
		#   o ExportCertData:
		#	 This exports two additional environment variables: SSL_CLIENT_CERT and
		#	 SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
		#	 server (always existing) and the client (only existing when client
		#	 authentication is used). This can be used to import the certificates
		#	 into CGI scripts.
		#   o StdEnvVars:
		#	 This exports the standard SSL/TLS related `SSL_*' environment variables.
		#	 Per default this exportation is switched off for performance reasons,
		#	 because the extraction step is an expensive operation and is usually
		#	 useless for serving static content. So one usually enables the
		#	 exportation for CGI and SSI requests only.
		#   o OptRenegotiate:
		#	 This enables optimized SSL connection renegotiation handling when SSL
		#	 directives are used in per-directory context.
		#SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
		<FilesMatch "\.(cgi|shtml|phtml|php)$">
				SSLOptions +StdEnvVars
		</FilesMatch>
		<Directory /usr/lib/cgi-bin>
				SSLOptions +StdEnvVars
		</Directory>

		#   SSL Protocol Adjustments:
		#   The safe and default but still SSL/TLS standard compliant shutdown
		#   approach is that mod_ssl sends the close notify alert but doesn't wait for
		#   the close notify alert from client. When you need a different shutdown
		#   approach you can use one of the following variables:
		#   o ssl-unclean-shutdown:
		#	 This forces an unclean shutdown when the connection is closed, i.e. no
		#	 SSL close notify alert is send or allowed to received.  This violates
		#	 the SSL/TLS standard but is needed for some brain-dead browsers. Use
		#	 this when you receive I/O errors because of the standard approach where
		#	 mod_ssl sends the close notify alert.
		#   o ssl-accurate-shutdown:
		#	 This forces an accurate shutdown when the connection is closed, i.e. a
		#	 SSL close notify alert is send and mod_ssl waits for the close notify
		#	 alert of the client. This is 100% SSL/TLS standard compliant, but in
		#	 practice often causes hanging connections with brain-dead browsers. Use
		#	 this only for browsers where you know that their SSL implementation
		#	 works correctly.
		#   Notice: Most problems of broken clients are also related to the HTTP
		#   keep-alive facility, so you usually additionally want to disable
		#   keep-alive for those clients, too. Use variable "nokeepalive" for this.
		#   Similarly, one has to force some clients to use HTTP/1.0 to workaround
		#   their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and
		#   "force-response-1.0" for this.
		BrowserMatch "MSIE [2-6]" \
				nokeepalive ssl-unclean-shutdown \
				downgrade-1.0 force-response-1.0
		# MSIE 7 and newer should be able to use keepalive
		BrowserMatch "MSIE [17-9]" ssl-unclean-shutdown

	</VirtualHost>
</IfModule>

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet

moncloud.monsites1.conf

 
<VirtualHost *:80>
	ServerAdmin webmaster@.moncloud.monsite1.fr
	ServerName moncloud.monsite1.fr
	ServerAlias moncloud.monsite1.fr
	
	DocumentRoot /var/www/moncloud.monsite1.fr
	<Directory />
		Options FollowSymLinks
		AllowOverride All
	</Directory>
	<Directory /var/www/moncloud.monsite1.fr>
		Options Indexes FollowSymLinks MultiViews
		AllowOverride All
		Order allow,deny
		allow from all
	</Directory>

	ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/
	<Directory "/usr/lib/cgi-bin">
		AllowOverride All
		Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
		Order allow,deny
		Allow from all
	</Directory>

	ErrorLog /var/log/apache2/error.log

	# Possible values include: debug, info, notice, warn, error, crit,
	# alert, emerg.
	LogLevel warn

	CustomLog /var/log/apache2/access.log combined

    Alias /doc/ "/usr/share/doc/"
    <Directory "/usr/share/doc/">
        Options Indexes MultiViews FollowSymLinks
        AllowOverride All
        Order deny,allow
        Deny from all
        Allow from 127.0.0.0/255.0.0.0 ::1/128
    </Directory>

</VirtualHost>

monsite1.conf

 
<VirtualHost *:80>
	ServerAdmin webmaster@monsite1.fr
	ServerName monsite1.fr
	ServerAlias monsite1.fr
	
	DocumentRoot /var/www/monsite1.fr
	<Directory />
		Options FollowSymLinks
		AllowOverride All
	</Directory>
	<Directory /var/www/monsite1.fr>
		Options Indexes FollowSymLinks MultiViews
		AllowOverride All
		Order allow,deny
		allow from all
	</Directory>

	ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/
	<Directory "/usr/lib/cgi-bin">
		AllowOverride All
		Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
		Order allow,deny
		Allow from all
	</Directory>

	ErrorLog /var/log/apache2/error.log

	# Possible values include: debug, info, notice, warn, error, crit,
	# alert, emerg.
	LogLevel warn

	CustomLog /var/log/apache2/access.log combined

    Alias /doc/ "/usr/share/doc/"
    <Directory "/usr/share/doc/">
        Options Indexes MultiViews FollowSymLinks
        AllowOverride All
        Order deny,allow
        Deny from all
        Allow from 127.0.0.0/255.0.0.0 ::1/128
    </Directory>

</VirtualHost>

Dernière modification par GhostSpirit (Le 01/07/2015, à 13:16)

---

Apprendre, comprendre, progresser, et apprendre aux autres, telle est ma devise
http://forum.ubuntu-fr.org/viewforum.php?id=171

bruno

Re : mauvaise redirection https pour owncloud

Il faut que tu lises ceci : http://httpd.apache.org/docs/2.2/vhosts/name-based.html

Tu comprendras ainsi que lorsque tu fais une requête vers https://moncloud.monsite1.fr (sur le port 443 donc), Apache ne trouve pas de directive ServerName correspondante et utilise donc l'hôte virtuel default-ssl.conf qui pointe sur /var/www/html

Si tu veux servir moncloud.monsite1.fr en HTTPS il faut que tu aies quelque part une configuration du type :

<VirtualHost *:443>
	ServerAdmin webmaster@.moncloud.monsite1.fr
	ServerName moncloud.monsite1.fr

        SSLCertificateFile	/chemin/vers/certif.crt
	SSLCertificateKeyFile /chemin/vers/clef/privee.key
	
	DocumentRoot /var/www/moncloud.monsite1.fr

	<Directory /var/www/moncloud.monsite1.fr>
…
…

En passant, cela ne sert à rien d'avoir des directives ServerName et ServerAlias identiques et dans un de tes hôtes la directive DocumentRoot n'est pas cohérente avec <Directory>

GhostSpirit

Re : mauvaise redirection https pour owncloud

Merci pour le lien.

Ce que je ne comprend pas, c'est que j'avais réussi à installer owncloud en https, j'ai suivi un bout de tuto mais cela ne marche plus. surement parce que je n'ai pas installer owncloud dans le répertoire standart.
d'après ce que j'ai compris il faut modifier .httaccess

je voudrais essayer cette méthode :
   

<    RewriteEngine On
    RewriteCond %{HTTPS} off
    RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}

mais je ne sais pas où je dois écrire ces lignes

Dernière modification par GhostSpirit (Le 01/07/2015, à 13:52)

---

Apprendre, comprendre, progresser, et apprendre aux autres, telle est ma devise
http://forum.ubuntu-fr.org/viewforum.php?id=171

bruno

Re : mauvaise redirection https pour owncloud

Il n' y a pas besoin de toucher aux fichiers .htaccess (le mieux est même de ne pas les utiliser lorsque l'on a la main sur la configuration du serveur). Et peu importe où est installé Owncloud du moment que DocumentRoot indique le bon dossier.

Avant de chercher à forcer une redirection vers le HTTPS, il faut d'abord qu'il fonctionne comme je te l'ai indiqué précédemment.