Bucle de redireccionamiento de Apache en la instalación de Drupal en el subdirectorio VHost solo en la URL raíz

Bucle de redireccionamiento de Apache en la instalación de Drupal en el subdirectorio VHost solo en la URL raíz

Actualmente tengo un problema con la página de inicio de nuestro sitio de producción debido a una instalación de Drupal que falla con "ERR_TOO_MANY_REDIRECTS".

Un poco de historia de nuestra configuración: en nuestro servidor, tenemos diferentes VHosts configurados para ejecutar diferentes aplicaciones.

La idea es que cada instalación se realice en un subdirectorio del nombre de dominio, como subdominio.example.com/app1 y subdominio.example.com/app2.

Ha estado funcionando durante casi un año y, de repente, solo la página de inicio de la instalación de Drupal comienza a realizar bucles de redireccionamiento (subdominio.ejemplo.com/app). El entorno de prueba está configurado exactamente de la misma manera y no muestra este comportamiento. Además, otras páginas dentro de la aplicación de producción se muestran sin problemas (subdominio.ejemplo.com/app/page).

La instalación se encuentra en el servidor en /var/www/app. Esto debería servir como raíz del documento para la instalación cuando se visita en subdominio.example.com/app/.

El VHOST para la instalación problemática tiene este aspecto:

<Directory "/var/www/app">
    #
    # 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
    # http://httpd.apache.org/docs/2.4/mod/core.html#options
    # for more information.
    #
    Options Indexes FollowSymLinks

    #
    # 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
    Order allow,deny
    Allow from all
    #
    # Controls who can get stuff from this server.
    #
    Require all granted
    RewriteEngine on
    RewriteBase /
    Include /var/www/app/.htaccess
</Directory>
NameVirtualHost *:80
<VirtualHost *:80>
    ServerName subdomain.example.com
    ServerPath /app
DocumentRoot /var/www/app
</VirtualHost>
# Set the Alias for the CLP installation
Alias "/app/" "/var/www/app/"
Alias "/app" "/var/www/app"

También tengo un archivo .htaccess dentro de cada uno de los VHOSTS para impulsar la redirección:

#
# Apache/PHP/Drupal settings:
#

SetEnvIfNoCase X-Forwarded-Proto https HTTPS=on

# Protect files and directories from prying eyes.
<FilesMatch "\.(engine|inc|info|install|make|module|profile|test|po|sh|.*sql|theme|tpl(\.php)?|xtmpl)(~|\.sw[op]|\.bak|\.orig|\.save)?$|^(\..*|Entries.*|Repository|Root|Tag|Template|composer\.(json|lock))$|^#.*#$|\.php(~|\.sw[op]|\.bak|\.orig\.save)$">
  Order allow,deny
</FilesMatch>

# Don't show directory listings for URLs which map to a directory.
Options -Indexes

# Follow symbolic links in this directory.
Options +FollowSymLinks

# Make Drupal handle any 404 errors.
# Relative to the DocumentRoot defined in httpd.conf
ErrorDocument 404 /app/index.php

# Set the default handler.
# Relative to the DocumentRoot defined in httpd.conf
DirectoryIndex /app/index.php /app/index.html /app/index.htm

# Override PHP settings that cannot be changed at runtime. See
# sites/default/default.settings.php and drupal_environment_initialize() in
# includes/bootstrap.inc for settings that can be changed at runtime.

php_value upload_max_filesize 500M
php_value post_max_size 500M
php_value memory_limit 500M
# PHP 5, Apache 1 and 2.
<IfModule mod_php5>
    php_flag magic_quotes_gpc                 off
    php_flag magic_quotes_sybase              off
    php_flag register_globals                 off
    php_flag session.auto_start               off
    php_value mbstring.http_input             pass
    php_value mbstring.http_output            pass
    php_flag mbstring.encoding_translation    off
</IfModule>

# Requires mod_expires to be enabled.
<IfModule mod_expires.c>
    # Enable expirations.
    ExpiresActive On

    # Cache all files for 2 weeks after access (A).
    ExpiresDefault A1209600

    <FilesMatch \.php$>
        # Do not allow PHP scripts to be cached unless they explicitly send cache
        # headers themselves. Otherwise all scripts would have to overwrite the
        # headers set by mod_expires if they want another caching behavior. This may
        # fail if an error occurs early in the bootstrap process, and it may cause
        # problems if a non-Drupal PHP file is installed in a subdirectory.
ExpiresActive Off
    </FilesMatch>
</IfModule>

# Various rewrite rules.
<IfModule mod_rewrite.c>
    RewriteEngine on
    # Set "protossl" to "s" if we were accessed via https://.  This is used later
    # if you enable "www." stripping or enforcement, in order to ensure that
    # you don't bounce between http and https.
    RewriteRule ^ - [E=protossl]
    RewriteCond %{HTTPS} on
    RewriteRule ^ - [E=protossl:s]

    # Make sure Authorization HTTP header is available to PHP
    # even when running as CGI or FastCGI.
    RewriteRule ^ - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

    # Block access to "hidden" directories whose names begin with a period. This
    # includes directories used by version control systems such as Subversion or
    # Git to store control files. Files whose names begin with a period, as well
    # as the control files used by CVS, are protected by the FilesMatch directive
    # above.
    #
    # NOTE: This only works when mod_rewrite is loaded. Without mod_rewrite, it is
    # not possible to block access to entire directories from .htaccess, because
    # <DirectoryMatch> is not allowed here.
    #
    # If you do not have mod_rewrite installed, you should remove these
    # directories from your webroot or otherwise protect them from being
    # downloaded.
    RewriteRule "/\.|^\.(?!well-known/)" - [F]

    # If your site can be accessed both with and without the 'www.' prefix, you
    # can use one of the following settings to redirect users to your preferred
    # URL, either WITH or WITHOUT the 'www.' prefix. Choose ONLY one option:
    #
    # To redirect all users to access the site WITH the 'www.' prefix,
    # (http://example.com/... will be redirected to http://www.example.com/...)
    # uncomment the following:
    # RewriteCond %{HTTP_HOST} .
    # RewriteCond %{HTTP_HOST} !^www\. [NC]
    # RewriteRule ^ http%{ENV:protossl}://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
    #
    # To redirect all users to access the site WITHOUT the 'www.' prefix,
    # (http://www.example.com/... will be redirected to http://example.com/...)
    # uncomment the following:
    # RewriteCond %{HTTP_HOST} ^www\.(.+)$ [NC]
    # RewriteRule ^ http%{ENV:protossl}://%1%{REQUEST_URI} [L,R=301]

    # Modify the RewriteBase if you are using Drupal in a subdirectory or in a
    # VirtualDocumentRoot and the rewrite rules are not working properly.
    # For example if your site is at http://example.com/drupal uncomment and
    # modify the following line:
    RewriteBase /app/
    #
    # If your site is running in a VirtualDocumentRoot at http://example.com/,
    # uncomment the following line:
    #RewriteBase /

    # Pass all requests not referring directly to files in the filesystem to
    # index.php. Clean URLs are handled in drupal_environment_initialize().
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_URI} !=/favicon.ico
    RewriteRule ^ index.php [L]

    # Rules to correctly serve gzip compressed CSS and JS files.
    # Requires both mod_rewrite and mod_headers to be enabled.
<IfModule mod_headers.c>
# Serve gzip compressed CSS files if they exist and the client accepts gzip.
RewriteCond %{HTTP:Accept-encoding} gzip
RewriteCond %{REQUEST_FILENAME}\.gz -s
RewriteRule ^(.*)\.css $1\.css\.gz [QSA]

# Serve gzip compressed JS files if they exist and the client accepts gzip.
RewriteCond %{HTTP:Accept-encoding} gzip
RewriteCond %{REQUEST_FILENAME}\.gz -s
RewriteRule ^(.*)\.js $1\.js\.gz [QSA]

# Serve correct content types, and prevent mod_deflate double gzip.
RewriteRule \.css\.gz$ - [T=text/css,E=no-gzip:1]
RewriteRule \.js\.gz$ - [T=text/javascript,E=no-gzip:1]

<FilesMatch "(\.js\.gz|\.css\.gz)$">
  # Serve correct encoding type.
  Header set Content-Encoding gzip
  # Force proxies to cache gzipped & non-gzipped css/js files separately.
  Header append Vary Accept-Encoding
</FilesMatch>
</IfModule>
RedirectMatch ^(.*)/app/course-page/CP([0-9]*)$ $1/app/course-page/$2
RedirectMatch ^(.*)/app/ramping-site/RS([0-9]*)$ $1/app/ramping-site/$2
RedirectMatch ^(.*)/app/content/BCTID([0-9]*)$ $1/app/content/$2
</IfModule>

# Add headers to all responses.
<IfModule mod_headers.c>
  # Disable content sniffing, since it's an attack vector.
  Header always set X-Content-Type-Options nosniff
</IfModule>

Llevo dos días con el servicio caído y no puedo encontrar una solución.

Respuesta1

Gracias por su aportación a todos ustedes. Resultó ser un archivo dañado en la máquina virtual que eventualmente provocó que fallara. Todavía no estoy seguro de qué era.

Si puedo descubrir qué se corrompió realmente, lo publicaré aquí como referencia.

Sin embargo, antes de fallar, Apache (HTTPD) deja de ejecutar PHP 7.0 en el navegador. Ejecutaría scripts PHP en la CLI, pero solo mostraría el texto PHP en los navegadores web. Unas horas más tarde, el servidor falló.

información relacionada