Dot-Htaccess
如何解決重定向問題
使用 cloudflare 後我面臨著大問題。我不是開發人員。我是一個簡單的人。我如何通過 htaccess 文件解決這個問題?😕 我目前的 htaccess 文件在這裡
# BEGIN LSCACHE ## LITESPEED WP CACHE PLUGIN - Do not edit the contents of this block! ## <IfModule LiteSpeed> RewriteEngine on CacheLookup on RewriteRule .* - [E=Cache-Control:no-autoflush] RewriteRule ^min/\w+\.(css|js) - [E=cache-control:no-vary] ### marker MOBILE start ### RewriteCond %{HTTP_USER_AGENT} Mobile|Android|Silk/|Kindle|BlackBerry|Opera\ Mini|Opera\ Mobi [NC] RewriteRule .* - [E=Cache-Control:vary=ismobile] ### marker MOBILE end ### ### marker CACHE RESOURCE start ### RewriteRule wp-content/.*/[^/]*(responsive|css|js|dynamic|loader|fonts)\.php - [E=cache-control:max-age=3600] ### marker CACHE RESOURCE end ### ### marker FAVICON start ### RewriteRule favicon\.ico$ - [E=cache-control:max-age=86400] ### marker FAVICON end ### ### marker WEBP start ### RewriteCond %{HTTP_ACCEPT} "image/webp" [or] RewriteCond %{HTTP_USER_AGENT} "Page Speed" RewriteRule .* - [E=Cache-Control:vary=%{ENV:LSCACHE_VARY_VALUE}+webp] ### marker WEBP end ### </IfModule> ## LITESPEED WP CACHE PLUGIN - Do not edit the contents of this block! ## # END LSCACHE # BEGIN NON_LSCACHE ## LITESPEED WP CACHE PLUGIN - Do not edit the contents of this block! ## ### marker BROWSER CACHE start ### <IfModule mod_expires.c> ExpiresActive on ExpiresByType application/pdf A2592000 ExpiresByType image/x-icon A2592000 ExpiresByType image/vnd.microsoft.icon A2592000 ExpiresByType image/svg+xml A2592000 ExpiresByType image/jpg A2592000 ExpiresByType image/jpeg A2592000 ExpiresByType image/png A2592000 ExpiresByType image/gif A2592000 ExpiresByType image/webp A2592000 ExpiresByType video/ogg A2592000 ExpiresByType audio/ogg A2592000 ExpiresByType video/mp4 A2592000 ExpiresByType video/webm A2592000 ExpiresByType text/css A2592000 ExpiresByType text/javascript A2592000 ExpiresByType application/javascript A2592000 ExpiresByType application/x-javascript A2592000 ExpiresByType application/x-font-ttf A2592000 ExpiresByType application/x-font-woff A2592000 ExpiresByType application/font-woff A2592000 ExpiresByType application/font-woff2 A2592000 ExpiresByType application/vnd.ms-fontobject A2592000 ExpiresByType font/ttf A2592000 ExpiresByType font/woff A2592000 ExpiresByType font/woff2 A2592000 </IfModule> ### marker BROWSER CACHE end ### ### marker MINIFY start ### <IfModule mod_rewrite.c> RewriteEngine on RewriteCond %{DOCUMENT_ROOT}%{REQUEST_URI} ^(.*)/min/(\w+)\.(css|js)$ RewriteCond %1/wp-content/cache/$2/$1.$2 -f RewriteRule min/(\w+)\.(css|js) wp-content/cache/$2/$1.$2 [L] </IfModule> ### marker MINIFY end ### ## LITESPEED WP CACHE PLUGIN - Do not edit the contents of this block! ## # END NON_LSCACHE # BEGIN WordPress # The directives (lines) between `BEGIN WordPress` and `END WordPress` are # dynamically generated, and should only be modified via WordPress filters. # Any changes to the directives between these markers will be overwritten. <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / RewriteRule ^index\.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] </IfModule> # END WordPress # php -- BEGIN cPanel-generated handler, do not edit # Set the “ea-php72” package as the default “PHP” programming language. <IfModule mime_module> AddHandler application/x-httpd-ea-php72 .php .php7 .phtml </IfModule> # php -- END cPanel-generated handler, do not edit
問題是重定向
http
到https
和https
到https://www
這似乎是由 WordPress 本身的程式碼引起的——因為
.htaccess
您發布的程式碼不包含任何這種性質的重定向。但是,您可以通過直接重定向到規範 URL(即。 )來“修復” 1 ,這自然會在*WordPress 啟動之前發生。
.htaccess``https://www
例如,在
.htaccess
文件的最頂部添加以下內容(example.com
您的域名在哪裡):RewriteCond %{HTTPS} !on [OR] RewriteCond %{HTTP_HOST} !^www\. RewriteRule ^ https://www.example.com%{REQUEST_URI} [R=302,L]
這會將尚未使用 HTTPS 或尚未用於 www 的任何請求重定向到 HTTPS + www。
請注意,首先使用 302(臨時)重定向對其進行測試,然後再將其更改為 301(永久)重定向,以避免任何潛在的記憶體問題。
您需要在測試前清除瀏覽器記憶體。
1請注意,這不一定是需要修復的問題。搜尋引擎(以及與此相關的使用者)可以毫無問題地處理這樣的短重定向鏈。這是一個邊緣案例,可以擷取手動在瀏覽器中輸入 URL 的使用者,或者在過去可能連結到錯誤/舊 URL 的第 3 方。請注意,如果您有意進入HSTS 預載入列表,那麼實際上需要像這樣的短重定向鏈,因為您必須在重定向到 www之前重定向到同一主機上的 HTTPS(因此,“gtmetrix”在此是錯誤*的案子)。