mod_rewrite htaccess enable allowoverride linux apache mod-rewrite

linux - enable - .htaccess no funciona(mod_rewrite)



mod_rewrite ubuntu server (16)

No he tenido suerte para que funcione mi .htaccess con mod_rewrite. Básicamente, lo único que trato de hacer es eliminar ''www'' de " http://www.example.com " y " https://www.example.com ".

Si hay algo que me falta (archivos conf, etc., hágamelo saber que lo actualizaré)

Aquí está mi archivo .htaccess (ubicado @ / var / www / site / trunk / html /)

Options +FollowSymLinks RewriteEngine on RewriteCond %{HTTP_HOST} ^www/.(.*) [NC] RewriteRule (.*) //%1/$1 [L,R=301]

Mi mod_rewrite está habilitado:

root@s15348441:/etc/apache2/mods-available# more rewrite.load LoadModule rewrite_module /usr/lib/apache2/modules/mod_rewrite.so

Mis archivos de configuración de apache:

apache2.conf

# # Based upon the NCSA server configuration files originally by Rob McCool. # # This is the main Apache server configuration file. It contains the # configuration directives that give the server its instructions. # See http://httpd.apache.org/docs/2.2/ for detailed information about # the directives. # # 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. # # The configuration directives are grouped into three basic sections: # 1. Directives that control the operation of the Apache server process as a # whole (the ''global environment''). # 2. Directives that define the parameters of the ''main'' or ''default'' server, # which responds to requests that aren''t handled by a virtual host. # These directives also provide default values for the settings # of all virtual hosts. # 3. Settings for virtual hosts, which allow Web requests to be sent to # different IP addresses or hostnames and have them handled by the # same Apache server process. # # 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 "/var/log/apache2/foo.log" # with ServerRoot set to "" will be interpreted by the # server as "//var/log/apache2/foo.log". # ### Section 1: Global Environment # # The directives in this section affect the overall operation of Apache, # such as the number of concurrent requests it can handle or where it # can find its configuration files. # # # ServerRoot: The top of the directory tree under which the server''s # configuration, error, and log files are kept. # # NOTE! If you intend to place this on an NFS (or otherwise network) # mounted filesystem then please read the LockFile documentation (available # at <URL:http://httpd.apache.org/docs-2.1/mod/mpm_common.html#lockfile>); # you will save yourself a lot of trouble. # # Do NOT add a slash at the end of the directory path. # ServerRoot "/etc/apache2" # # The accept serialization lock file MUST BE STORED ON A LOCAL DISK. # #<IfModule !mpm_winnt.c> #<IfModule !mpm_netware.c> LockFile /var/lock/apache2/accept.lock #</IfModule> #</IfModule> # # PidFile: The file in which the server should record its process # identification number when it starts. # This needs to be set in /etc/apache2/envvars # PidFile ${APACHE_PID_FILE} # # Timeout: The number of seconds before receives and sends time out. # Timeout 300 # # KeepAlive: Whether or not to allow persistent connections (more than # one request per connection). Set to "Off" to deactivate. # KeepAlive On # # MaxKeepAliveRequests: The maximum number of requests to allow # during a persistent connection. Set to 0 to allow an unlimited amount. # We recommend you leave this number high, for maximum performance. # MaxKeepAliveRequests 100 # # KeepAliveTimeout: Number of seconds to wait for the next request from the # same client on the same connection. # KeepAliveTimeout 15 ## ## Server-Pool Size Regulation (MPM specific) ## # prefork MPM # StartServers: number of server processes to start # MinSpareServers: minimum number of server processes which are kept spare # MaxSpareServers: maximum number of server processes which are kept spare # MaxClients: maximum number of server processes allowed to start # MaxRequestsPerChild: maximum number of requests a server process serves <IfModule mpm_prefork_module> StartServers 5 MinSpareServers 5 MaxSpareServers 10 MaxClients 150 MaxRequestsPerChild 0 </IfModule> # worker MPM # StartServers: initial number of server processes to start # MaxClients: maximum number of simultaneous client connections # MinSpareThreads: minimum number of worker threads which are kept spare # MaxSpareThreads: maximum number of worker threads which are kept spare # ThreadsPerChild: constant number of worker threads in each server process # MaxRequestsPerChild: maximum number of requests a server process serves <IfModule mpm_worker_module> StartServers 2 MaxClients 150 MinSpareThreads 25 MaxSpareThreads 75 ThreadsPerChild 25 MaxRequestsPerChild 0 </IfModule> # These need to be set in /etc/apache2/envvars User ${APACHE_RUN_USER} Group ${APACHE_RUN_GROUP} # # AccessFileName: The name of the file to look for in each directory # for additional configuration directives. See also the AllowOverride # directive. # AccessFileName .htaccess # # The following lines prevent .htaccess and .htpasswd files from being # viewed by Web clients. # <Files ~ "^/.ht"> Order allow,deny Deny from all </Files> # # DefaultType is 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 # # HostnameLookups: Log the names of clients or just their IP addresses # e.g., www.apache.org (on) or 204.62.129.132 (off). # The default is off because it''d be overall better for the net if people # had to knowingly turn this feature on, since enabling it means that # each client request will result in AT LEAST one lookup request to the # nameserver. # HostnameLookups Off # 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/apache2/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 # Include module configuration: Include /etc/apache2/mods-enabled/*.load Include /etc/apache2/mods-enabled/*.conf # Include all the user configurations: Include /etc/apache2/httpd.conf # Include ports listing Include /etc/apache2/ports.conf # # The following directives define some format nicknames for use with # a CustomLog directive (see below). # If you are behind a reverse proxy, you might want to change %h into %{X-Forwarded-For}i # LogFormat "%h %l %u %t /"%r/" %>s %b /"%{Referer}i/" /"%{User-Agent}i/"" combined LogFormat "%h %l %u %t /"%r/" %>s %b" common LogFormat "%{Referer}i -> %U" referer LogFormat "%{User-agent}i" agent # # ServerTokens # This directive configures what you return as the Server HTTP response # Header. The default is ''Full'' which sends information about the OS-Type # and compiled in modules. # Set to one of: Full | OS | Minor | Minimal | Major | Prod # where Full conveys the most information, and Prod the least. # ServerTokens Full # # Optionally add a line containing the server version and virtual host # name to server-generated pages (internal error documents, FTP directory # listings, mod_status and mod_info output etc., but not CGI generated # documents or custom error documents). # Set to "EMail" to also include a mailto: link to the ServerAdmin. # Set to one of: On | Off | EMail # ServerSignature On # # Customizable error responses come in three flavors: # 1) plain text 2) local redirects 3) external redirects # # Some examples: #ErrorDocument 500 "The server made a boo boo." #ErrorDocument 404 /missing.html #ErrorDocument 404 "/cgi-bin/missing_handler.pl" #ErrorDocument 402 http://www.example.com/subscription_info.html # # # Putting this all together, we can internationalize error responses. # # We use Alias to redirect any /error/HTTP_<error>.html.var response to # our collection of by-error message multi-language collections. We use # includes to substitute the appropriate text. # # You can modify the messages'' appearance without changing any of the # default HTTP_<error>.html.var files by adding the line: # # Alias /error/include/ "/your/include/path/" # # which allows you to create your own set of files by starting with the # /usr/share/apache2/error/include/ files and copying them to /your/include/path/, # even on a per-VirtualHost basis. The default include files will display # your Apache version number and your ServerAdmin email address regardless # of the setting of ServerSignature. # # The internationalized error documents require mod_alias, mod_include # and mod_negotiation. To activate them, uncomment the following 30 lines. # Alias /error/ "/usr/share/apache2/error/" # # <Directory "/usr/share/apache2/error"> # AllowOverride None # Options IncludesNoExec # AddOutputFilter Includes html # AddHandler type-map var # Order allow,deny # Allow from all # LanguagePriority en cs de es fr it nl sv pt-br ro # ForceLanguagePriority Prefer Fallback # </Directory> # # ErrorDocument 400 /error/HTTP_BAD_REQUEST.html.var # ErrorDocument 401 /error/HTTP_UNAUTHORIZED.html.var # ErrorDocument 403 /error/HTTP_FORBIDDEN.html.var # ErrorDocument 404 /error/HTTP_NOT_FOUND.html.var # ErrorDocument 405 /error/HTTP_METHOD_NOT_ALLOWED.html.var # ErrorDocument 408 /error/HTTP_REQUEST_TIME_OUT.html.var # ErrorDocument 410 /error/HTTP_GONE.html.var # ErrorDocument 411 /error/HTTP_LENGTH_REQUIRED.html.var # ErrorDocument 412 /error/HTTP_PRECONDITION_FAILED.html.var # ErrorDocument 413 /error/HTTP_REQUEST_ENTITY_TOO_LARGE.html.var # ErrorDocument 414 /error/HTTP_REQUEST_URI_TOO_LARGE.html.var # ErrorDocument 415 /error/HTTP_UNSUPPORTED_MEDIA_TYPE.html.var # ErrorDocument 500 /error/HTTP_INTERNAL_SERVER_ERROR.html.var # ErrorDocument 501 /error/HTTP_NOT_IMPLEMENTED.html.var # ErrorDocument 502 /error/HTTP_BAD_GATEWAY.html.var # ErrorDocument 503 /error/HTTP_SERVICE_UNAVAILABLE.html.var # ErrorDocument 506 /error/HTTP_VARIANT_ALSO_VARIES.html.var # Include of directories ignores editors'' and dpkg''s backup files, # see README.Debian for details. # Include generic snippets of statements Include /etc/apache2/conf.d/ # Include the virtual host configurations: Include /etc/apache2/sites-enabled/

Mi archivo de configuración predeterminado para www en apache

NameVirtualHost *:80 <VirtualHost *:80> ServerAdmin [email protected] #SSLEnable #SSLVerifyClient none #SSLCertificateFile /usr/local/ssl/crt/public.crt #SSLCertificateKeyFile /usr/local/ssl/private/private.key DocumentRoot /var/www/site/trunk/html <Directory /> Options FollowSymLinks AllowOverride all </Directory> <Directory /var/www/site/trunk/html> 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 None 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 ServerSignature On Alias /doc/ "/usr/share/doc/" <Directory "/usr/share/doc/"> Options Indexes MultiViews FollowSymLinks AllowOverride None Order deny,allow Deny from all Allow from 127.0.0.0/255.0.0.0 ::1/128 </Directory> </VirtualHost>

Mi archivo de configuración ssl

NameVirtualHost *:443 <VirtualHost *:443> ServerAdmin [email protected] #SSLEnable #SSLVerifyClient none #SSLCertificateFile /usr/local/ssl/crt/public.crt #SSLCertificateKeyFile /usr/local/ssl/private/private.key DocumentRoot /var/www/site/trunk/html <Directory /> Options FollowSymLinks AllowOverride all </Directory> <Directory /var/www/site/trunk/html> 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 None 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 SSLEngine On SSLCertificateFile /usr/local/ssl/crt/public.crt SSLCertificateKeyFile /usr/local/ssl/private/private.key CustomLog /var/log/apache2/access.log combined ServerSignature On Alias /doc/ "/usr/share/doc/" <Directory "/usr/share/doc/"> Options Indexes MultiViews FollowSymLinks AllowOverride None Order deny,allow Deny from all Allow from 127.0.0.0/255.0.0.0 ::1/128 </Directory> </VirtualHost>

Mi /etc/apache2/httpd.conf está en blanco

El directorio /etc/apache2/conf.d no tiene nada más que un archivo (charset)

contenido de /etc/apache2/conf.dcharset

# Read the documentation before enabling AddDefaultCharset. # In general, it is only a good idea if you know that all your files # have this encoding. It will override any encoding given in the files # in meta http-equiv or xml encoding tags. #AddDefaultCharset UTF-8

Mi error de apache

[Wed Jun 03 00:12:31 2009] [error] [client 216.168.43.234] client sent HTTP/1.1 request without hostname (see RFC2616 section 14.23): /w00tw00t.at.ISC.SANS.DFind:) [Wed Jun 03 05:03:51 2009] [error] [client 99.247.237.46] File does not exist: /var/www/site/trunk/html/favicon.ico [Wed Jun 03 05:03:54 2009] [error] [client 99.247.237.46] File does not exist: /var/www/site/trunk/html/favicon.ico [Wed Jun 03 05:13:48 2009] [error] [client 99.247.237.46] File does not exist: /var/www/site/trunk/html/favicon.ico [Wed Jun 03 05:13:51 2009] [error] [client 99.247.237.46] File does not exist: /var/www/site/trunk/html/favicon.ico [Wed Jun 03 05:13:54 2009] [error] [client 99.247.237.46] File does not exist: /var/www/site/trunk/html/favicon.ico [Wed Jun 03 05:13:57 2009] [error] [client 99.247.237.46] File does not exist: /var/www/site/trunk/html/favicon.ico [Wed Jun 03 05:17:28 2009] [error] [client 99.247.237.46] File does not exist: /var/www/site/trunk/html/favicon.ico [Wed Jun 03 05:26:23 2009] [notice] caught SIGWINCH, shutting down gracefully [Wed Jun 03 05:26:34 2009] [notice] Apache/2.2.8 (Ubuntu) PHP/5.2.4-2ubuntu5.6 with Suhosin-Patch mod_ssl/2.2.8 OpenSSL/0.9.8g configured -- resuming normal operations [Wed Jun 03 06:03:41 2009] [notice] caught SIGWINCH, shutting down gracefully [Wed Jun 03 06:03:51 2009] [notice] Apache/2.2.8 (Ubuntu) PHP/5.2.4-2ubuntu5.6 with Suhosin-Patch mod_ssl/2.2.8 OpenSSL/0.9.8g configured -- resuming normal operations [Wed Jun 03 06:25:07 2009] [notice] caught SIGWINCH, shutting down gracefully [Wed Jun 03 06:25:17 2009] [notice] Apache/2.2.8 (Ubuntu) PHP/5.2.4-2ubuntu5.6 with Suhosin-Patch mod_ssl/2.2.8 OpenSSL/0.9.8g configured -- resuming normal operations [Wed Jun 03 12:09:25 2009] [error] [client 61.139.105.163] File does not exist: /var/www/site/trunk/html/fastenv [Wed Jun 03 15:04:42 2009] [notice] Graceful restart requested, doing restart [Wed Jun 03 15:04:43 2009] [notice] Apache/2.2.8 (Ubuntu) PHP/5.2.4-2ubuntu5.6 with Suhosin-Patch mod_ssl/2.2.8 OpenSSL/0.9.8g configured -- resuming normal operations [Wed Jun 03 15:29:51 2009] [error] [client 99.247.237.46] File does not exist: /var/www/site/trunk/html/favicon.ico [Wed Jun 03 15:29:54 2009] [error] [client 99.247.237.46] File does not exist: /var/www/site/trunk/html/favicon.ico [Wed Jun 03 15:30:32 2009] [error] [client 99.247.237.46] File does not exist: /var/www/site/trunk/html/favicon.ico [Wed Jun 03 15:45:54 2009] [notice] caught SIGWINCH, shutting down gracefully [Wed Jun 03 15:46:05 2009] [notice] Apache/2.2.8 (Ubuntu) PHP/5.2.4-2ubuntu5.6 with Suhosin-Patch mod_ssl/2.2.8 OpenSSL/0.9.8g configured -- resuming normal operations

¿Cuáles son los permisos de archivo para su archivo .htaccess?

No estoy seguro, pero creo que tiene que ser 644.

¿Qué tal esta regla de reescritura?

RewriteEngine On RewriteCond %{HTTP_HOST} ^www.example.com$ [NC] RewriteRule ^(.*)$ http://example.com/$1 [R=301,L]

Como dijo Vinko,

RewriteLog "/tmp/rewrite.log" RewriteLogLevel 9

y mira ese archivo.

De lo contrario, aquí está el código que estamos usando para redirigir desde zirconium.zrs.hr/~zatemas a zatemas.zrs.hr:

RewriteEngine on # For sites running on a port other than 80 RewriteCond %{HTTP_HOST} !^zatemas/.zrs/.hr [NC] RewriteCond %{HTTP_HOST} !^$ RewriteCond %{SERVER_PORT} !^80$ RewriteRule ^/~zatemas/(.*) http://zatemas.zrs.hr:%{SERVER_PORT}/$1 [L,R] # And for a site running on port 80 RewriteCond %{HTTP_HOST} !^192/.168/.1/.24 [NC] RewriteCond %{HTTP_HOST} !^zatemas/.zrs/.hr [NC] RewriteCond %{HTTP_HOST} !^$ RewriteRule ^/~zatemas/(.*) http://zatemas.zrs.hr/$1 [L,R]

He visto en toda la web que las personas detectan HTTPS principalmente al ver si el puerto es 443. La documentación de mod_rewrite dice que debe haber una HTTPS variable configurada para RewriteCond %{HTTPS} ^on$ o desactivarse, de manera apropiada: supongo que debe RewriteCond %{HTTPS} ^on$ para prueba si está encendido.

También tenga cuidado: las directivas .htaccess para la reescritura de URL no funcionan bien si está accediendo a los archivos en el directorio de inicio del usuario, por ejemplo example.com/~nombre de usuario /. Sin embargo, eso no debería molestarte según tu situación. Mi código anterior se coloca en la configuración del servidor principal, en la sección VirtualHost (más precisamente, en /etc/apache2/sites-enabled/000-default , pero eso es específico de Debian y se fusiona en la configuración principal).

En mi caso, cambié en httpd.conf:

AllowOverride None

a

AllowOverride All

y funciona.

En primer lugar, verifique que mod_rewrite se esté cargando. Puedes hacer eso con apache2ctl:

[root@host ~]# apache2ctl -t -D DUMP_MODULES 2>&1 |grep rewrite rewrite_module (shared)

Si no es así, es posible que deba ejecutar ''a2enmod rewrite''

Luego, prueba para ver si tu archivo .htaccess está siendo leído. Normalmente lo hago poniendo algo de basura dentro del archivo .htaccess, luego cargando una página en ese directorio en mi navegador y verificando que obtengo un error de 500

Como nota adicional, como han mencionado otros, si tiene la capacidad de modificar su configuración de Apache directamente, debe poner allí las Reglas de Reescritura en lugar del archivo .htaccess, ya que es menos eficiente. Apache tiene que decidir primero en qué directorio buscar el archivo .htaccess, luego leerlo, luego realizar las reescrituras. Si RewriteRules está especificado dentro de sus directivas VirtualHost, entonces puede hacerlo antes de encontrar el archivo .htaccess. Especificarlos dentro de su VirtualHost también significa que no importa si su archivo .htaccess se está leyendo. Se vería algo como esto:

<VirtualHost *:80> .... existing config .... RewriteEngine on RewriteCond %{HTTP_HOST} ^www/.(.*) [NC] RewriteRule (.*) http://%1/$1 [L,R=301] </VirtualHost> <VirtualHost *:443> .... existing config .... RewriteEngine on RewriteCond %{HTTP_HOST} ^www/.(.*) [NC] RewriteRule (.*) https://%1/$1 [L,R=301] </VirtualHost>

Ninguna de las soluciones anteriores funcionó para mí. Estoy ejecutando CentOS utilizando el contexto de directorio para Apache ... sin VirtualHosts ni nada. Nada de lo que probé funcionó hasta que noté que NameVirtualHost estaba activado por defecto en mi configuración ... después de apagarlo todo parece estar funcionando bien.

O esto:

RewriteEngine on RewriteCond %{HTTP_HOST} ^www/.(.*) [NC] RewriteCond %{HTTP_PORT} =443 RewriteRule (.*) https://%1/$1 [L,R=301] RewriteCond %{HTTP_HOST} ^www/.(.*) [NC] RewriteRule (.*) http://%1/$1 [L,R=301]

Para mí, faltaba un enlace simbólico

ln -s /etc/apache2/mods-available/rewrite.load /etc/apache2/mods-enabled/rewrite.load

Parece que estás diciendo que tu mod_rewrite no funciona en absoluto. Aquí hay algunas cosas para probar:

Dijiste que estaba habilitado, pero la información proporcionada:

root@s15348441:/etc/apache2/mods-available# more rewrite.load LoadModule rewrite_module /usr/lib/apache2/modules/mod_rewrite.so

Simplemente lo muestra debajo de la carpeta "mods-available", lo que significa que está instalado, pero no necesariamente encendido. Si está habilitado, debe vincularse simbólicamente en la carpeta "mods-enabled" (necesitarás a2enmod si no está allí)

Si está habilitado y se ha reiniciado, el siguiente paso sería habilitar la función de registro de la reescritura mod; esta es una excelente herramienta para la depuración.

Editado para agregar: puede mover la reescritura mod a la configuración base. Si tiene acceso a él, se recomienda poner su configuración en la sección base de todos modos (ver here ). También es más fácil determinar si tiene algo que ver con mod_rewrite (como que las autorizaciones de permiso se confunden) o es simplemente un problema de htaccess.

Continuando: (@Vinko Vrsalovic tiene razón acerca de que este es un medio de depuración difícil) Si lo movió a su configuración base y todavía no funcionó, entonces estamos en algo, ha eliminado la porción .htaccess. Debería publicar la nueva configuración, junto con los registros de reescritura. Si no obtuvo un registro de reescritura, entonces 1) su configuración no se ha cargado (necesita reiniciar apache) o 2) no está accediendo a la sección de configuración que cree que es

Prueba este pequeño truco:

RewriteEngine on RewriteCond %{HTTPS}s/%{HTTP_HOST} ^(on(s)|[^/]+)/www/.(.+) [NC] RewriteRule ^ http%2://%3%{REQUEST_URI} [L,R=301]

Puedes probar fácilmente si tu htaccess está siendo leído o no:

  • Ponga basura en ella, como:

    Options +FollowSymLinks This is garbage RewriteEngine on RewriteCond %{HTTP_HOST} ^www/.(.*) [NC] RewriteRule (.*) //%1/$1 [L,R=301]

    Si obtiene un error de 500 (Error interno del servidor), entonces SE ESTÁ LEYENDO.

    Si es así, debe habilitar RewriteLog en la configuración del servidor principal (no en .htaccess) de esta manera:

    RewriteLog "/tmp/rewrite.log" RewriteLogLevel 9

Y luego verifique el archivo /tmp/rewrite.log para ver qué está pasando. Reporte con resultados.

( no es un buen medio de depuración, IRC es mejor para eso, prueba #[email protected])

Buena suerte.

Tuve el mismo problema y esto desperdició mis 5 horas para solucionarlo.

Entonces, para usar mod_rewrite puedes escribir el siguiente comando en la terminal:

a2enmod rewrite

Luego reinicia tu Apache.

Tuve el problema al hacer que mod_rewrite funcione en mi nueva instalación nueva de CentOS 6. Nada funcionó para mí, hasta que accidentalmente vi que había dos AllowOverride dentro de httpd.conf . Uno dentro de <Directory /> y otro dentro de <Directory "/var/www/html"> . Cambié ambos valores a Todos y luego funcionó. Espero que ayude a alguien!

PD: No usé hosts virtuales

Tuve un problema similar, esto es lo que funcionó para mí.

En su httpd.conf, bajo hosts virtuales, asegúrese de tener ambos:

ServerName domain.com

ServerAlias ​​www.domain.com

AMBOS en VirtualHost *: 80 Y VirtualHost *: 443

Tuve un problema similar. Modificación de memoria habilitada, los permisos de .htaccess son correctos, AllowOverride establecido en Todos, pero no se lee .htaccess. Después de horas de dolor y buscando una respuesta, este es mi problema: (espero que esto ayude a cualquiera)

He tenido habilitado otro sitio de host virtual además del que estaba probando y compartía una raíz de directorio común (/ var / www) y AllowOverride se configuró en none para el otro sitio. La solución fue simplemente deshabilitar el otro sitio con "a2dissite"

RewriteEngine on RewriteCond %{HTTPS} =on RewriteCond %{HTTP_HOST} ^www/.(.*) [NC] RewriteRule ^(.*)$ https://%1$1 [L,R=301] RewriteCond %{HTTP_HOST} ^www/.(.*) [NC] RewriteRule ^(.*)$ http://%1$1 [L,R=301]

Dos ligeros cambios de otras respuestas:

La referencia inversa %1 en RewriteRule toma de la última coincidencia RewriteCond , por lo que la comprobación de HTTPS debe venir antes de la verificación de www en el nombre de host.

%1$1 no necesita una barra en el centro, porque la obtendrá de la coincidencia de ruta en RewriteRule .

Un último consejo: dado que usted tiene control sobre las secciones de VirtualHost en la configuración principal de Apache, sería más rápido poner estas reglas allí. Además, los dividiría, colocando el HTTP simple en *: 80 y HTTPS en *: 443, lo que significa que puede eliminar RewriteCond %{HTTPS} =on completo, ya que solo se aplicaría a las solicitudes destinadas a ese host virtual. .