There are at aleast two ways you can block other user agents and allow only a few. This can be done by editing the .htaccess file in the root directory of your WordPress website. Option 1 Using mod_rewrite, add the code below at the top of your .htaccess file. <IfModule mod_rewrite.c> RewriteEngine on RewriteCond %{HTTP_USER_AGENT} … Read more
To effectively disable that condition for that one URL-path, you will need to add another rule immediately before the rule in question. ie. before the # Abuse Agent Blocking comment. For example: # Allow an empty User-Agent for requests that start “/wp-content/uploads/xmls” RewriteCond %{HTTP_USER_AGENT} ^$ RewriteRule ^wp-content/uploads/xmls – [S=1] # Abuse Agent Blocking RewriteCond %{HTTP_USER_AGENT} … Read more
I’m honestly struggling to comprehend this failure state – I believe I’ve reproduced the issue locally, and in my testing the RewriteRule directive hits but then WordPress processes the original input, resulting in a fairly catch-all attachment rewrite producing a query for a non-existent attachment. I may continue playing with it to try and figure … Read more
As per @Milo, I’m adding my comment above as an answer… Try going to example.com/blog/wp-admin/options-permalink.php. That should work, because the php file actually exists. If so, try updating your permalink options to a friendly version, like “Day and name”. This will put a new .htaccess in the blog directory — I’m thinking that that new … Read more
This is possible, and it actually should be very easy for you to do. There are lots of ways that you could have this setup, depending on if your server is using cPanel, Plesk, etc. At its most basic, right now, your Apache virtual host points to your main web directory, maybe something like /var/www/, … Read more
The .htaccess catches requests before WordPress is even started. That’s much faster than any plugin. For a handful of redirects I wouldn’t install a plugin. You need that only in cases when the server cannot know the new address, for example if you rename permalinks (slugs) automatically (you shouldn’t ;)).
Ok guys, I did further research. Basically, all I had to do was add “Satisfy Any” argument. So the main .htaccess file looked like the one I posted in my initial thread. Then for the specific folder, I created a new .htaccess file (/folder/.htaccess). Then added this: <Files wp-login.php> Satisfy Any </Files> Much thanks to … Read more
Comment out the following by adding hash tags before it #RewriteCond %{REQUEST_URI} !^/images/ #RewriteCond %{REQUEST_URI} !^/images #RewriteCond %{REQUEST_URI} !.*images(.*) and see if that helps.
You ask: How does that work ? As far as I can read it, it only specifies not to rewrite certain urls (using -), These files are included within the WordPress PHP scripts, so there’s no need to access them in the browser, but notice the rewrite flags. Here’s some information on the F, L … Read more
When a URL is processed by WordPress, its index.php script is loaded with the path to the requested page. Because in this case the index.php script is always found, a normal 404 error will never trigger (via ErrorDocument 404 …). If the requested URL does not match a page that WP knows about, WP will … Read more