This adds in the region of an extra 1.5 – 2 seconds load time. These redirects alone should not be adding “an extra 1.5 – 2 seconds load time”. If it is then you would seem to have other problems with your server response time or slow network speeds. After the initial request, any DNS … Read more
RewriteRule ^\d{4}/\d{2}/(.*).html+.* http://www.example.com/$1/ [R=301,L] This does look as if it should “work”, although there are a few things that can be tidied, and the query string (ie. m=1 or m=0) will remain on the URL. Also, make sure you have cleared your browser cache before testing as 301s are cached hard by the browser. It … Read more
The non-www to www redirect is most certainly being handled (later) by WordPress. Your existing redirect in .htaccess is HTTP to HTTPS only, on the same host – which is actually the preferred (read: necessary) way if you have any plans to implement HSTS in the near future. So, this is not necessarily an “error”. … Read more
Redirect non-existent subpages to second part of url
Redirect permanent / http://www.example.com/wordpress/ You can’t use a mod_alias Redirect directive in this way to redirect to a subdirectory on the same site because the Redirect directive is prefix-matching and everything after the match is appended to the target (which is how this directive is able to redirect all URL-paths to the same URL-path at … Read more
Sometimes the user login cache can get in the way, you could try adding this: wp_cache_delete($user_id, ‘users’); $user = new WP_User($user_id); wp_cache_delete($user->user_login, ‘userlogins’);
You’ve put the HTTP to HTTPS (and canonical www) redirect in the wrong place. It should go before the WordPress front-controller. In fact, it should go before the # BEGIN WordPress section to avoid any chance of it being overwritten by WordPress in future updates. To be honest, I’m a bit surprised that redirect would … Read more
It’s not clear from the .htaccess files you’ve posted why you can’t access files/folders outside of your WordPress installation (inside the /websiteWP subdirectory). In fact, you shouldn’t need to add specific exceptions in order to access physical files, since these directives shouldn’t apply to physical files. However, your .htaccess files are misconfigured… If the WordPress … Read more
You need to check if WordPress Address (URL) and Site Address (URL) are configured correctly. Go to > Settings > General / see image below: Enter your URL with the port number: http://localhost:8888/csdev This will solve WordPress unnecessary redirecting you.
Try adding this code to .htaccess: RedirectMatch 404 /\d{4}/\d{2}/\d{2}/(.*)\.html http://example.com/$1 It should fix the issue.