I just did a test and it seems like the rewrite rules imply ^ if you do not specify it. In my test I found: rule ‘foo’ matched url ‘foo’ rule ‘^foo’ matched url ‘foo’ rule ‘foo’ did not match url ‘afoo’ rule ‘^foo’ did not much url ‘afoo’ rule ‘.*foo’ matched url ‘afoo’ So … Read more
RewriteCond %{HTTP_COOKIE} !.*wordpress_logged_in.*$ [NC] RewriteCond %{REQUEST_URI} ^(.*?/?)purchase.php RewriteRule . https://%{HTTP_HOST}%1/registrationurl [L,QSA] This will result in a 302 (temporary) redirect to /purchaseads//registrationurl – note the double-slash. This double-slash is passed through to the $_SERVER[‘REQUEST_URI’] variable that WordPress uses to route the URL. So, this may result in WP not being able to route the request. You … Read more
You appear to be denying access to PHP files, which would explain why you are denied access to PHP files: <FilesMatch “.(py|exe|php)$”> Order allow,deny Deny from all </FilesMatch> What is the purpose of this?
Try the following mod_rewrite directives instead at the top of your root .htaccess file (before the # BEGIN WordPress section): # Reject any user requests that are not prefixed “/wp-json” RewriteCond %{ENV:REDIRECT_STATUS} ^$ RewriteRule !wp-json($|/) – [F] Requested URLs that are not prefixed /wp-json (or /wp-json/) are rejected with a 403 Forbidden. The RewriteCond directive … Read more
The directives in .htaccess (on your application server) would seem to be working as expected. Yet I keep getting requests on that file. Blocking the request in .htaccess doesn’t stop the request reaching your server (and being logged). As you can see from the log entry, it is being “blocked” and your server is responding … Read more
You don’t appear to have allowed .htaccess overrides in the <VirtualHost *:443> container, so .htaccess is effectively disabled. Without .htaccess you’ll naturally get 404s for anything other than the homepage if you are using “pretty” permalinks. (.htaccess is not required for requests to the homepage, since index.php is served by mod_dir which is no doubt … Read more
Save your existing .htaccess file by renaming it to backup.htaccess & then re-save your permalinks which will create a new .htaccess file. That solves issues most of the time.
This has been answered many times. Search this site, as toscho points out above. And see Ben Word – Hide WordPress, who shows how to: 1 – Clean up the output of wp_head and removing the generator from RSS feeds 2 – Hide /wp-content/ by rewriting static theme assets (CSS, JS, and images), rewriting the … Read more
Answer: Don’t disable it, use it to do the redirection you want. If you have a subdomain install, then you cannot do this at all, the www is a subdomain. If you have a sub-directory install and want all the sites to be www, then edit your wp-config.php and change the DOMAIN_CURRENT_SITE to be your … Read more
It looks as though what you’re asking is to redirect /page/n to the homepage, this can be accomplished with the RedirectMatch directive. So: RedirectMatch 301 ^/page/(.*) http://www.my-site.com/ would redirect all traffic from /page/n to the homepage.