Got it working using the following RewriteEngine On RewriteCond %{HTTP_HOST} ^(?:www\.)?example\.com$ [NC] RewriteRule ^secure-payment$ https://domain.com/secure-payment [L,NC,R=301] RewriteRule ^blog/news/please-help$ https://domain.com/blog/news/please-help [L,NC,R=301] RewriteRule ^ https://domain.com/rebrand-explained/ [L,NC,R=301]
You can potentially use redirects to achieve this, it may not be the most ideal or stable solution, and could cause problems with your site. This is why you’re seeing a “too many redirects” error. Every time WordPress loads, it checks if the requested URL is supposed to be the admin URL. If not, it … Read more
It might be useful to let the web server write .htaccess during initial site setup, e.g. when you’re setting up rewrite rules (as it said) or if you’re setting up a multisite network. Once you’ve done that though it no longer needs to edit the file so it would make sense to secure it the … Read more
WordPress site down for my IP only after trying to implement .htaccess whitelist
Browser Caching .htaccess
Permalinks not working on debian with OVH
Post pages are redirecting to the 404 page in wordpress
WP-Include rewrite directory
I installed the SameSite plug-in which mimics the default PHP setcookie behavior and adds the additional parameter (samesite) to the cookie. I set the plug-in configuration in wp-config.php with: define( ‘WP_SAMESITE_COOKIE’, ‘None’ ); By setting the configuration of samesite=None, browsers will not enforce SameSite rules that are used to prevent CSRF. From the Mozilla blog: … Read more
I use this for my htaccess force-SSL rule on my multisites (actually, on all sites). RewriteEngine On RewriteCond %{HTTPS} off RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301] Not sure, but bet that off is better than !=on .A resource you can use to test htaccess rules is https://htaccess.madewithlove.com/ .