Do these lines mean HTTPS urls will not be cached? Well, it certainly means that on most servers that have an SSL cert installed, the URL will not be rewritten to /wp-content/cache/all/<requested-URL-path>/index.html. If that means the cache will be bypassed, then yes, it prevents caching. The idea of not caching HTTPS requests would seem to … Read more
Plain permalinks of the form /?p=14523 (or /index.php?p=14523) don’t necessarily need any .htaccess file since they don’t require mod_rewrite to rewrite the URL (unlike the the custom permalinks you mention). However, for a URL of the form /?p=14523 (as opposed to /index.php?p=14523), where you don’t explicitly state the index document (ie. index.php) in the URL … Read more
You can do something like the following at the top of your .htaccess file to replace all – with + that occur after the /search/ path segment in the requested URL: RewriteRule ^(search/[^-]*)-([^-]*-.*) /$1+$2 [N] RewriteRule ^(search/[^-]*)-([^-]*)$ /$1+$2 [R=302,L] The first RewriteRule loops (internally) until all except 1 hyphen has been replaced with +. The … Read more
In my cloudfare settings, i found that SSL encryption over cloudfare was “off”. I turned it to “Full Strict”.. Then the problem was fixed. But i am still not sure why i was getting redirect loop in mobile browsers only.
The old method works for me, and any requests result in a 403 status response instead of execution of the php script. I’ve not checked your 2nd method, but if it works it will similarly respond with 403 denied/forbidden. To test you simply have to insert the URL of your “wp-config.php” in the address bar … Read more
Am I missing something simple? You need the L flag (to prevent further processing) and this directive should go at the very top of your existing .htaccess file (ie. before the # BEGIN WordPress section). Unless you have already defined an appropriate RewriteBase directive (the WordPress front-controller usually has this), then you also need to … Read more
It’s not clear from what you have posted why you are getting a redirect loop. We would need to see the rest of .htaccess file. However …. You may be getting a conflict with existing mod_rewrite (ie. RewriteRule) directives. Redirect is a mod_alias directive. You no doubt have existing mod_rewrite directives with the WordPress front-controller. … Read more
If WordPress is installed in the directory /dir1/dir2 and the corresponding .htaccess file is also in that subdirectory, ie. /dir1/dir2/.htaccess, then the .htaccess file should look something like: # BEGIN WordPress <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 … Read more
You can do something like the following at the top of your .htaccess file in the document root using mod_rewrite before the WordPress front-controller. Note that since you have two distinct patterns (root directory to /music and everything else to the root directory on the other domain) then you’ll need to two rules. RewriteEngine On … Read more
I would approach it like so: Remove all of these plugins. Decide if you want to use the address with or without www. prefix as default. Install SSL correctly, without a plugin. (So change all of the URLs in database and make sure your site works correctly, its address is set properly and there is … Read more