I found a simple plugin that did the job for me. This is what my .htaccess file looks like now for my sub-domain: <IfModule mod_rewrite.c> RewriteEngine on RewriteCond %{HTTPS} !=on [NC] RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L] # BEGIN WordPress #RewriteEngine On RewriteBase / RewriteRule ^index\.php$ – [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php … Read more
I solved it by logging in into admin panel and saving site URL with a trailing slash at the end.
When the directive is included as part of the WordPress directives It simply needs to go before the WordPress front-controller. In fact, you should not include this as “part of the WordPress directives” as WP itself tries to maintain this block of code and could override your custom directives in a future update. You should … Read more
ExpiresByType text/x-javascript “access plus 1 month” ExpiresByType text/javascript “access plus 1 month” ExpiresByType application/x-javascript “access plus 14 days” In order to determine the correct mime-type to use you need to look at the Content-Type HTTP response header from your server (using your browser). The default for JavaScript files is application/javascript – which you’ve not included … 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
The only way I managed to get this to work was with the following in the .htaccess of the /site/ directory: RewriteBase \ RedirectMatch 301 ^/site/$ /$1 RedirectMatch 301 ^/site/(?!wp-admin/|wp-content/|wp-includes/)(.*)$ /$1 Whilst I am aware that RewriteRule ^site/ /$1 [R=301,NC,L] should have worked, and that RewriteRule ^site/(.*)$ /$1 [R=301,NC,L] should have also worked (according to … Read more
Maybe try something like this.. .htaccess on your root: # 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 .htaccess inside your /wordpress/ directory: # BEGIN WordPress <IfModule mod_rewrite.c> RewriteEngine On RewriteBase /wordpress/ RewriteRule ^index\.php$ – [L] RewriteCond … Read more