J'ai configuré notre serveur Apache pour utiliser UserDir
.
Cela signifie que nos URL sont:
http://dev.server.com/~username/drupal/html/
Avant nos URL étaient:
http://dev.server.com/drupal/html/
Dans le second cas, je n'ai jamais eu à définir RewriteBase
. Le défaut a juste fonctionné.
Maintenant, je dois définir RewriteBase
pour le 1er cas:
RewriteBase /~username/drupal/html/
Est-ce que tu sais pourquoi? Le ~username
pose-t-il un problème à drupal?
Fichier .htaccess qui ne fonctionne pas (RewriteBase
non défini)
<IfModule mod_rewrite.c>
RewriteEngine on
# 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 "(^|/)\." - [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} !^www\. [NC]
# RewriteRule ^ http://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://%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 /~cmuench/rocdocs/html/
#
# 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>
</IfModule>
La directive RewriteBase
contrôle le préfixe du chemin (l'URL de base) qui est rajouté lorsque vous avez une substitution de chemin relative dans le RewriteRule
. Le code suivant (index.php
) est une substitution de chemin relatif:
RewriteRule ^ index.php [L]
Si vous n'indiquez pas explicitement le RewriteBase
, le préfixe par répertoire (le chemin du système de fichiers qui mène à ce fichier .htaccess) est automatiquement ajouté. Puisque ~username
ne fait pas partie du chemin physique sur le système de fichiers, il ne fait pas partie du préfixe par répertoire et n'est donc pas ajouté à la substitution. Cependant, il est nécessaire dans ce cas pour construire une URL valide. Vous devez donc explicitement l'inclure dans la directive RewriteBase
.