.htaccess funktioniert nicht

Debian macht sich hervorragend als Web- und Mailserver. Schau auch in den " Tipps und Tricks"-Bereich.
Antworten
Benutzeravatar
jmar83
Beiträge: 404
Registriert: 20.06.2013 20:20:15

.htaccess funktioniert nicht

Beitrag von jmar83 » 04.12.2019 11:13:38

/etc/apache2/sites-available/000-default.conf:

Code: Alles auswählen

<VirtualHost *:80>
	# The ServerName directive sets the request scheme, hostname and port that
	# the server uses to identify itself. This is used when creating
	# redirection URLs. In the context of virtual hosts, the ServerName
	# specifies what hostname must appear in the request's Host: header to
	# match this virtual host. For the default virtual host (this file) this
	# value is not decisive as it is used as a last resort host regardless.
	# However, you must set it for any further virtual host explicitly.
	ServerName abc.li
	ServerAlias www.abc.li
	ServerAlias xyz.ch
	ServerAlias www.xyz.ch

	ServerAdmin webmaster@localhost
	DocumentRoot /var/www/html

	# J.M., 2019-12-04 {
        <Directory /var/www/html>
          Options Indexes FollowSymLinks
          AllowOverride All
          Require all granted
        </Directory>
        # } J.M., 2019-12-04

	# 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

RewriteEngine on

#RewriteCond %{SERVER_NAME} =xyz.ch [OR]
#RewriteCond %{SERVER_NAME} =www.xyz.ch [OR]

RewriteCond %{SERVER_NAME} =abc.li [OR]
RewriteCond %{SERVER_NAME} =www.abc.li

RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]

</VirtualHost>

#<Directory /var/www/html/>
#    Options Indexes FollowSymLinks
#    AllowOverride All
#    Require all granted
#</Directory>

# J.M., 2018-12-06 {
RequestHeader append Expires "Tue, 03 Jul 2001 06:00:00 GMT"
RequestHeader append Last-Modified "{now} GMT"
RequestHeader append Cache-Control "no-store, no-cache, must-revalidate, max-age=0"
RequestHeader append Cache-Control "post-check=0, pre-check=0"
RequestHeader append Pragma "no-cache"
# } J.M., 2018-12-06

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



/etc/apache2/sites-available/000-default-le-ssl.conf:

Code: Alles auswählen

<IfModule mod_ssl.c>
<VirtualHost *:443>
	# The ServerName directive sets the request scheme, hostname and port that
	# the server uses to identify itself. This is used when creating
	# redirection URLs. In the context of virtual hosts, the ServerName
	# specifies what hostname must appear in the request's Host: header to
	# match this virtual host. For the default virtual host (this file) this
	# value is not decisive as it is used as a last resort host regardless.
	# However, you must set it for any further virtual host explicitly.
	#ServerName www.example.com
	ServerName abc.li
	ServerAlias www.abc.li
	ServerAlias xyz.ch
	ServerAlias www.xyz.ch

	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


Include /etc/letsencrypt/options-ssl-apache.conf
Include /etc/letsencrypt/options-ssl-apache.conf
Include /etc/letsencrypt/options-ssl-apache.conf
Include /etc/letsencrypt/options-ssl-apache.conf
SSLCertificateFile /etc/letsencrypt/live/abc.li/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/abc.li/privkey.pem
</VirtualHost>
</IfModule>
<IfModule mod_ssl.c>
<VirtualHost *:80>
	# The ServerName directive sets the request scheme, hostname and port that
	# the server uses to identify itself. This is used when creating
	# redirection URLs. In the context of virtual hosts, the ServerName
	# specifies what hostname must appear in the request's Host: header to
	# match this virtual host. For the default virtual host (this file) this
	# value is not decisive as it is used as a last resort host regardless.
	# However, you must set it for any further virtual host explicitly.
	ServerName abc.li
	ServerAlias www.abc.li
	ServerAlias xyz.ch
	ServerAlias www.xyz.ch

	ServerAdmin webmaster@localhost
	DocumentRoot /var/www/html
	
        # J.M., 2019-12-04 {
        <Directory /var/www/html>
          Options Indexes FollowSymLinks
          AllowOverride All
          Require all granted
        </Directory>
        # } J.M., 2019-12-04


	# 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

RewriteEngine on
RewriteCond %{SERVER_NAME} =abc.li [OR]
RewriteCond %{SERVER_NAME} =www.abc.li
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]



</VirtualHost>
</IfModule>

/etc/apache2/sites-available/default-ssl.conf:

Code: Alles auswählen

<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

	</VirtualHost>
 <Directory /var/www/html/>
    Options Indexes FollowSymLinks
    AllowOverride All
    Require all granted
</Directory>
</IfModule>

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


.htaccess:

Code: Alles auswählen

<FilesMatch ".*\.(ini)$">
  Order allow,deny
  Deny from all
</FilesMatch>

<ifModule mod_headers.c>
  Header set X-Robots-Tag "noindex, nofollow"
</ifModule>

Options +Indexes

#@__HCP_END__@#
# Anything after the comment above is left alone


Resultat: 403 anstelle auflisten der Dateien wegen `Options +Indexes` in der .htaccess-Datei:

[image]
https://i.ibb.co/vQ6qJsr/Unbenannt.png
[/image]
Freundliche Grüsse, Jan

Benutzeravatar
jmar83
Beiträge: 404
Registriert: 20.06.2013 20:20:15

Re: .htaccess funktioniert nicht

Beitrag von jmar83 » 04.12.2019 11:15:16

...es heisst ja praktisch im ganzen Internet man müssen diesen Block verwenden, aber so scheint das nicht zu gehen?

Code: Alles auswählen

<Directory /var/www/html>
          Options Indexes FollowSymLinks
          AllowOverride All
          Require all granted
        </Directory>
Freundliche Grüsse, Jan

Benutzeravatar
jmar83
Beiträge: 404
Registriert: 20.06.2013 20:20:15

Re: .htaccess funktioniert nicht

Beitrag von jmar83 » 04.12.2019 11:16:17

Und wie kriege ich Bilder hier rein, für das ist [image]...[/image]...??

Scheint so ziemlich funktionslos zu sein:

`[image]
https://i.ibb.co/vQ6qJsr/Unbenannt.png
[/image]`


???
Freundliche Grüsse, Jan

Benutzeravatar
Lord_Carlos
Beiträge: 4653
Registriert: 30.04.2006 17:58:52
Lizenz eigener Beiträge: GNU Free Documentation License
Wohnort: Dänemark

Re: .htaccess funktioniert nicht

Beitrag von Lord_Carlos » 04.12.2019 11:29:08

jmar83 hat geschrieben: ↑ zum Beitrag ↑
04.12.2019 11:16:17
Und wie kriege ich Bilder hier rein, für das ist [image]...[/image]...??

Scheint so ziemlich funktionslos zu sein:
Mit [ img ]
[image] ist fuer Bilder aus der Galerie.

Aber das Bild hilft auch nicht viel weiter. Und etwas gross.
Sag einfach der Webserver schmeist ein 403.

Code: Alles auswählen

╔═╗┬ ┬┌─┐┌┬┐┌─┐┌┬┐╔╦╗
╚═╗└┬┘└─┐ │ ├┤ │││ ║║
╚═╝ ┴ └─┘ ┴ └─┘┴ ┴═╩╝ rockt das Forum!

Benutzeravatar
jmar83
Beiträge: 404
Registriert: 20.06.2013 20:20:15

Re: .htaccess funktioniert nicht

Beitrag von jmar83 » 04.12.2019 11:32:06

Vielen Dank, würde offenbar klappen, allerdings: "Deine Bilder dürfen maximal 1000 Pixel hoch sein."...
Freundliche Grüsse, Jan

Benutzeravatar
mig
Beiträge: 108
Registriert: 26.02.2003 13:21:58
Wohnort: wien
Kontaktdaten:

Re: .htaccess funktioniert nicht

Beitrag von mig » 11.12.2019 12:26:45

Hallo
Schau dir mal den Stern in deiner .htaccess an

Code: Alles auswählen

<FilesMatch "\.(ini)$">
Sollte doch reichen, oder?
LG
Michael

Benutzeravatar
jmar83
Beiträge: 404
Registriert: 20.06.2013 20:20:15

Re: .htaccess funktioniert nicht

Beitrag von jmar83 » 11.12.2019 13:00:58

Danke für Feedback! :-)

Dieser Eintrag ist vom Hoster hostpoint.ch, damit man über das .ini-File spez. Sachen (z.B. PHP Logging) regeln kann.

Nun habe ich alles aus dem .htaccess gelöscht und nur den Eintrag `blabla` eingefügt.

Resultat: Die Webseite läuft immer noch, eigentlich sollte es doch nun bodenbös crashen mit einer Meldung "misconfiguration" oder so... tut es aber leider nicht.

Fazit: .htaccess ist mit der aktuellen Konfiguration wirkungslos, sonst würde es mit dem `blabla`-Eintrag crashen, vor allem wenn die .htaccess im Webroot ist...?
Freundliche Grüsse, Jan

Benutzeravatar
mig
Beiträge: 108
Registriert: 26.02.2003 13:21:58
Wohnort: wien
Kontaktdaten:

Re: .htaccess funktioniert nicht

Beitrag von mig » 11.12.2019 14:59:30

Hallo

Wie kommst Du auf crashen (abstürzen)?
Es würde dir bloß einen Internal Server Error anzeigen, läuft aber weiter

LG
Michael

Benutzeravatar
mig
Beiträge: 108
Registriert: 26.02.2003 13:21:58
Wohnort: wien
Kontaktdaten:

Re: .htaccess funktioniert nicht

Beitrag von mig » 11.12.2019 15:18:20

Hallo nochmal

Hast da mal deinen ssl vhost von le angeschaut, und wo ist da dein "AllowOverride All" ?

Welcher deiner multiplen vhosts sind überhaupt aktiv?

LG
Michael

Antworten