4
better alternatives like Apache Virtualhosts or something.
If you have access to the server-config, then you can use the Alias directive in the vHost to route all requests for /content/images to /wp-content/images.
For example:
Alias "/content/images/" "/wp-content/images"
Now, a request for /content/images/example.jpg would be sent to /wp-content/images/...
4
I would use mod_rewrite and put this in your main .htaccess near the top, just below RewriteEngine On:
RewriteCond %{REQUEST_URI} ^/u/.*
RewriteRule !\.(png|jpg|jpeg|gif|svg)$ - [R=404,L]
Using a rewrite rule, shows a 404 error directly at the URL rather than redirect to it. The RewriteCond ensures that only one directory is affected. The ! negates the ...
answered Dec 27 '19 at 11:52
2
What you are seeing is default behaviour on Apache.
when I enter random subdirectories, such as /index.php/asdfghjk
/asdfghjk is an additional path-segment in the URL. It's not strictly a "subdirectory". (Directories and subdirectories relate to a filesystem. The URL does not necessarily map directly to the filesystem.)
When additional path segments ...
2
Found the solution through .htaccess
Never sure if it's the best, but it works:
RewriteRule ^([_0-9a-zA-Z-]+/)?content/(.*) /wp-content/$2 [QSA,L]
2
So, is a redirect to another page with 410 code fine?
A redirect is not necessary. Define a custom 410 error document:
ErrorDocument 410 /error-docs/e410.php
And trigger the 410 in .htaccess, as you did before:
RewriteRule ^deleted/ - [G]
The G flag is simply a shortcut for R=410 and the L flag is not required (it is implied when using a status code ...
1
I expect www.filmstore.sandwiches.org to go to sandwiches.org, ...
This does not work, but sends me to filmstore.net, which I think is the default behaviour for multiple cPanel domains.
Ah, but the "problem" here is that the www.filmstore subdomain maps to the /filmstore subdirectory off the main domains document root (as stated in comments) - this ...
1
RewriteCond %{REQUEST_FILENAME} !^/PhP/?$
RewriteCond %{REQUEST_FILENAME} !^/forms/?$
RewriteCond %{REQUEST_URI} !^/PhP/?$
RewriteCond %{REQUEST_URI} !^/forms/?$
You don't need to check against both REQUEST_FILENAME and REQUEST_URI - you're just repeating the same check. It's easier to use REQUEST_URI (the URL-path) in this instance.
The ...
1
It sounds like you may have put the directives in the wrong place in your .htaccess file. The HTTP to HTTPS redirect needs to go near the top, before any other rewrites.
The nature of your URLs suggest you are using a front-controller type pattern and rewriting requests to a common script. However, the "homepage" does not need to be rewritten (since mod_dir ...
1
It would seem "the problem" is in your PHP code, not .htaccess as you seem to suggest.
RewriteRule ^(.+)$ index.php?page=$1 [QSA,L]
All requests are rewritten to index.php (your "front-controller") which then routes your URLs. It is this PHP script that determines whether /login or /login/asdasdasd, etc. resolve to a valid page on your site. This has ...
Only top voted, non community-wiki answers of a minimum length are eligible
