Working code for one file:
RewriteRule ^cookiestatement.php/?$ /m_cookiestatement.php [R,L]
I would like all php-files be redirect to its own filename but with the prefix m_
I can make it work for one file, but need it to do it for all .php files
RewriteRule ^cookiestatement.php/?$ /m_cookiestatement.php [R,L]
so
index.php --> m_index.php
contact.php --> m_contact.php
etc...
Well, you need to use a regular expression to match the requests, not a literal string. So something like the following, though you probably still have to adjust it to your setup:
RewriteEngine on
RewriteCond m_%{REQUEST_FILENAME} -f
RewriteRule ^/?(.*)\.php/?$ /m_$1.php [R=302]
It is a good idea to start out with a 302 temporary redirection and only change that to a 301 permanent redirection later, once you are certain everything is correctly set up. That prevents caching issues while trying things out...
This rule will work likewise in the http servers host configuration or inside a dynamic configuration file (".htaccess" file). Obviously the rewriting module needs to be loaded inside the http server and enabled in the http host. In case you use a dynamic configuration file you need to take care that it's interpretation is enabled at all in the host configuration and that it is located in the host's DOCUMENT_ROOT folder.
And a general remark: you should always prefer to place such rules in the http servers host configuration instead of using dynamic configuration files (".htaccess"). Those dynamic configuration files add complexity, are often a cause of unexpected behavior, hard to debug and they really slow down the http server. They are only provided as a last option for situations where you do not have access to the real http servers host configuration (read: really cheap service providers) or for applications insisting on writing their own rules (which is an obvious security nightmare).
Related
I am searching for a few hours on how to redirect all .php files to the file without the .php.
I know there is surely a fast answer for this but I have really trouble finding it.
How can I say that if someone loads mysite.com/mysubfolder/mysecondsub/myfile.php goes to mysite.com/mysubfolder/mysecondsub/myfile?
Like a normal rewrite except the URL PHP redirects to the one without the PHP extension.
(using .htaccess if possible and mod_rewrite)
I configured Apache2.conf to allow overwrites so that I am able to use .htacess.
It works when I use something like this post htaccess remove index.php from url
But the thing is that it works if I write mysite.com/url, but if I write mysite.com/url.php it does not redirect to mysite/url (which is what I want) I tried a few solutions but still no idea.
This probably is what you are looking for:
RewriteEngine on
RewriteRule ^/?(.+)\.php$ /$1 [R=301]
RewriteCond %{REQUEST_URI} !\.php$
RewriteCond %{REQUEST_FILENAME}.php -f
RewriteRule ^/?(.+)$ /$1.php [END]
It is a good idea to start out with a 302 temporary redirection and only change that to a 301 permanent redirection later, once you are certain everything is correctly set up. That prevents caching issues while trying things out...
In case you receive an internal server error (http status 500) using the rule above then chances are that you operate a very old version of the apache http server. You will see a definite hint to an unsupported [END] flag in your http servers error log file in that case. You can either try to upgrade or use the older [L] flag, it probably will work the same in this situation, though that depends a bit on your setup.
This implementation will work likewise in the http servers host configuration or inside a distributed configuration file (".htaccess" file). Obviously the rewriting module needs to be loaded inside the http server and enabled in the http host. In case you use a distributed configuration file you need to take care that it's interpretation is enabled at all in the host configuration and that it is located in the host's DOCUMENT_ROOT folder.
And a general remark: you should always prefer to place such rules in the http servers host configuration instead of using distributed configuration files (".htaccess"). Those distributed configuration files add complexity, are often a cause of unexpected behavior, hard to debug and they really slow down the http server. They are only provided as a last option for situations where you do not have access to the real http servers host configuration (read: really cheap service providers) or for applications insisting on writing their own rules (which is an obvious security nightmare).
A bit of a newbie question, how can I redirect a URL like this one: http://example.com.ar to http://example.com.ar/pictures/ using .htaccess ?
or would it be easier to make a rule that searches the entire request URL and adds a /pictures/ when not found?
I have tried:
RewriteBase /
RewriteCond %{HTTP_HOST} example.com.ar [NC]
RewriteRule ^(.*)$ http://www.example.com.ar/pictures/ [R=301,NC]
But it didn't work :/
Sounds pretty straight forward. You would have found hundreds of existing examples...
RewriteEngine on
RewriteRule ^/?$ /pictures/ [R=301]
It is a good idea to start out with a 302 temporary redirection and only change that to a 301 permanent redirection later, once you are certain everything is correctly set up. That prevents caching issues while trying things out...
This implementation will work likewise in the http servers host configuration or inside a dynamic configuration file (".htaccess" file). Obviously the rewriting module needs to be loaded inside the http server and enabled in the http host. In case you use a dynamic configuration file you need to take care that it's interpretation is enabled at all in the host configuration and that it is located in the host's DOCUMENT_ROOT folder.
And a general remark: you should always prefer to place such rules in the http servers host configuration instead of using dynamic configuration files (".htaccess"). Those dynamic configuration files add complexity, are often a cause of unexpected behavior, hard to debug and they really slow down the http server. They are only provided as a last option for situations where you do not have access to the real http servers host configuration (read: really cheap service providers) or for applications insisting on writing their own rules (which is an obvious security nightmare).
I want to create a redirect in my htaccess file. From URL with index.php to page without index.php, but only for one specific folder "buy-new-cars".
For example:
from example.com/buy-new-cars/index.php to example.com/buy-new-cars/
I try to add those lines.But this didn't work.
RewriteCond %{THE_REQUEST} /index\.php [NC]
RewriteRule ^(buy-new-cars/.+)index\.php$ /$1 [L,R=302,NC,NE]
Your issue is the RewriteCond you use which does not make sense.
Here is a version with some additional modifications:
RewriteEngine on
RewriteRule ^/?buy-new-cars/(.+)/index\.php$ /buy-new-cars/$1 [R=302,NC]
It is a good idea to start out with a 302 temporary redirection and only change that to a 301 permanent redirection later, once you are certain everything is correctly set up. That prevents caching issues while trying things out...
This rule will work likewise in the http servers host configuration or inside a dynamic configuration file (".htaccess" file). Obviously the rewriting module needs to be loaded inside the http server and enabled in the http host. In case you use a dynamic configuration file you need to take care that it's interpretation is enabled at all in the host configuration and that it is located in the host's DOCUMENT_ROOT folder.
And a general remark: you should always prefer to place such rules in the http servers host configuration instead of using dynamic configuration files (".htaccess"). Those dynamic configuration files add complexity, are often a cause of unexpected behavior, hard to debug and they really slow down the http server. They are only provided as a last option for situations where you do not have access to the real http servers host configuration (read: really cheap service providers) or for applications insisting on writing their own rules (which is an obvious security nightmare).
I'm trying to create a site whereby I can specify links as follows:
https://www.example.com/wildcard/parameter
I would like the above link to load the index.php file in the /wildcard directory and pass the parameter to the index file as index.php?type=parameter
However have the rule so that the subdirectory name could be anything.
I've tried numerous htaccess examples, however they either load the root index.php (homepage) file or return a requested url not found message
Essentially I would like:
https://example.com/wildcard/parameter
to behave the exact same way as
https://example.com/wildcard/index.php?type=parameter
But be flexible enough allow the subdirectory to have any name.
Can anyone help?
This should point you into the right direction:
RewriteEngine on
RewriteCond %{REQUEST_URI} ^/([^/]+)/(\w+)/?$
RewriteCond /%1 -d
RewriteCond /%1/index.php -f
RewriteRule ^ /%1/index.php?type=%2 [END]
In case you receive an internal server error (http status 500) using the rule above then chances are that you operate a very old version of the apache http server. You will see a definite hint to an unsupported [END] flag in your http servers error log file in that case. You can either try to upgrade or use the older [L] flag, it probably will work the same in this situation, though that depends a bit on your setup.
This rule will work likewise in the http servers host configuration or inside a dynamic configuration file (".htaccess" file). Obviously the rewriting module needs to be loaded inside the http server and enabled in the http host. In case you use a dynamic configuration file you need to take care that it's interpretation is enabled at all in the host configuration and that it is located in the host's DOCUMENT_ROOT folder.
And a general remark: you should always prefer to place such rules in the http servers host configuration instead of using dynamic configuration files (".htaccess"). Those dynamic configuration files add complexity, are often a cause of unexpected behavior, hard to debug and they really slow down the http server. They are only provided as a last option for situations where you do not have access to the real http servers host configuration (read: really cheap service providers) or for applications insisting on writing their own rules (which is an obvious security nightmare).
I'm trying to transfer over
www.old.example/ecards/birthday-ecards/all
which no longer exists to
https://www.new.example/static-ecards/company-birthday-ecards.html
When using .htaccess to complete this I'm getting it redirecting to
https://www.new.example/static-ecards/company-birthday-ecards.htmlecards/birthday-ecards/all
So it's adding this to the end of the URL ecards/birthday-ecards/all which is not needed.
I'm a noob with this and not a dev! Please advise.
I have tried
Redirect 301 "/old-folder/" "http://www.new.example/new-page.html"
Redirect 301 "/old-page.html" "http://www.new.example/new-page.html"
This probably is what you are looking for:
RewriteEngine on
RewriteCond %{HTTP_HOST} ^(www\.)?old\.example$
RewriteRule ^/?ecards/birthday-ecards/all$ https://www.new.example/static-ecards/company-birthday-ecards.html [R=301]
It is a good idea to start out with a 302 temporary redirection and only change that to a 301 permanent redirection later, once you are certain everything is correctly set up. That prevents caching issues while trying things out...
This rule will work likewise in the http servers host configuration or inside a dynamic configuration file (".htaccess" file). Obviously the rewriting module needs to be loaded inside the http server and enabled in the http host. In case you use a dynamic configuration file you need to take care that it's interpretation is enabled at all in the host configuration and that it is located in the host's DOCUMENT_ROOT folder.
And a general remark: you should always prefer to place such rules in the http servers host configuration instead of using dynamic configuration files (".htaccess"). Those dynamic configuration files add complexity, are often a cause of unexpected behavior, hard to debug and they really slow down the http server. They are only provided as a last option for situations where you do not have access to the real http servers host configuration (read: really cheap service providers) or for applications insisting on writing their own rules (which is an obvious security nightmare).
Add this rule on top of old.example .htaccess file
RewriteEngine On
RewriteBase /
RewriteRule ^ecards/birthday-ecards/all$ https://www.new.example/static-ecards/company-birthday-ecards.html [R=301,L]