I am tired of seeing my urls look dirty eg. http://localhost/test/postsingle?tk=Ben Affleck and Jennifer Garner File For Divorce Amid Reconciliation Rumors
so I am currently trying to make it look like this eg
http://localhost/test/postsingle/Ben Affleck and Jennifer Garner File For Divorce Amid Reconciliation Rumors
But its not working this my htacess config below
Please I will be really grateful for an answer
RewriteEngine On
RewriteCond %{SCRIPT_FILENAME} !-d
RewriteCond %{SCRIPT_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME}.php -f
RewriteRule ^(.*)$ $1.php
RewriteRule ^politicssingle/(\d+)*$ ./politicssingle?tk=$1
RewriteRule ^postsingle/(\d+)*$ ./postsingle?tk=$1
RewriteRule ^search/(.*)$ ./search?query=$1
Though I've seen related questions here but they're not helping
There is no rule in that file that even tries to rewrite the requests you ask about. So why should they get rewritten?
I'd say that you probably need to replace the first rewrite rule like that:
RewriteEngine On
RewriteCond %{SCRIPT_FILENAME} !-d
RewriteCond %{SCRIPT_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME}.php -f
RewriteRule ^/?test/postsingle/(.+)/? /test/postsingle?tk=$1 [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).
Related
I have webpages processed by php. When they're finished processing and i get a html-file output. This file is saved in a directory called "cache".
e.g.
www.domain.tld/list.html (browser-url)
www.domain.tld/cache/list.html (cached-file)
My actual problem is, that i have no clue how I could change the htaccess-file to work out the problem.
How can I apply that the RewriteCond will check first if the "/list.html"-file exists in that folder (cache) and then (if yes): return the file and (if not) just continue to the other conditions which will in the end redirect to index.php.
But i need to keep the rule, that it have to check if the file exists anyway (without that cache-folder)
This is causing errors:
RewriteCond cache/%{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php?/$1 [L,QSA]
How is that possible?
Some of the pages are processed for about 20-30 seconds or more. This is why I want to save them after processing and then deliver the already finished site to save time.
This should do what you ask:
RewriteEngine on
RewriteCond %{REQUEST_URI} ^/(.+)$
RewriteCond %{DOCUMENT_ROOT}/cache/%1 -f
RewriteRule ^ /cache/%1 [END]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^/?(.*)$ index.php?/$1 [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 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).
So I was wondering how can I make it where I have a directory for say domain.com/main/ and in that /main I have license.php with .htaccess how am I able to make it where I can do domain.com/main/view/license/(license) and it shows them domain.com/license.php?id={license} ive tried this and it doesn't work
This is my current .htaccess that I use that im trying to make it work with
<IfModule mod_rewrite.c>
RewriteRule ^/view/license/([a-zA-Z0-9\-/\.]+)/?$ license.php?id=$1 [L]
</IfModule>
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME}\.php -f
RewriteRule ^(.*)$ $1.php [NC,L]
RewriteEngine On
RewriteCond %{HTTPS} !on
RewriteCond %{REQUEST_URI} !^/[0-9]+\..+\.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/\.well-known/pki-validation/[A-F0-9]{32}\.txt(?:\ Comodo\ DCV)?$
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]```
Implement this rule in either a dynamic configuration file (".htaccess" style file) in the http server's DOCUMENT_ROOT folder, or, preferably, in the real host configuration:
RewriteEngine on
RewriteRule ^/?main/view/license/?$ /license.php [END]
RewriteRule ^/?main/view/license/([^/]+)/?$ /license.php?id=$1 [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 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).
Use
RewriteRule ^main/view/license/([a-zA-Z0-9\-/\.]+)/?$ license.php?id=$1 [L]
Adding main to the rule, and removing the first slash.
I am trying to remove the index.php?url=controller/method/parem
I just want to remove the index.php?url= thats it but its not working.
Now its look like this :
http://localhost/ServerSide/index.php?url=FrameWork/Index/category
I want
http://localhost/ServerSide/FrameWork/Index/category
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-l
RewriteRule ^(.+)$ index.php?url=$1 [QSA, L]
If you are using CodeIgniter then this solution works for me.
https://www.formget.com/codeigniter-htaccess-remove-index-php/
I think this is roughly what you are looking for:
RewriteEngine On
RewriteRule ^/?ServerSide/(.*)$ /ServerSide/index.php?url=$1 [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 want to map links like https://website.com/test/STRING to https://website.com/test/STRING.png, how to do it with .htaccess?
Options All -Indexes -MultiViews
RewriteEngine on
RewriteBase /test/
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{DOCUMENT_ROOT}/test/%1.png -f
RewriteRule ^([^/]+)/?$ /$1.png [NC,L]
but it is not working
I guess this is what you are looking for:
RewriteEngine on
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} ^/test/([^/]+)/?$
RewriteCond %{DOCUMENT_ROOT}/test/%1.png -f
RewriteRule ^ /test/%1.png [END]
There are alternatives obviously, this is just a suggestion. 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 seeting up a new website and want to rewrite some files with parameter in the urls.
The site isn't live right now and unfortunaly i haven't lots of experience in mod_rewrite.
So whats my Problem:
I have two files: category.php and single.php
on my index i have a menu that refers to all categories via url paramater.
For instance on sitename.com/index.php you find links to:
sitename.com/category.php?c=First
sitename.com/category.php?c=Second
sitename.com/category.php?c=Third
and so on
On sitename.com/category.php?c=First for instance you find a list of all posts that refer to category first and linked to:
sitename.com/single.php?c=Frist&name=name1
sitename.com/single.php?c=Frist&name=name2
sitename.com/single.php?c=Second&name=name3
sitename.com/single.php?c=Third&name=name4
and so on
Now i try to rewirte the urls to the following structure:
sitename.com/category.php?c=First => sitename.com/First
sitename.com/category.php?c=Second=> sitename.com/Second
sitename.com/single.php?c=Frist&name=name2 =>sitename.com/First/name2
sitename.com/single.php?c=Second&name=name3 =>sitename.com/Second/name3
I used the following Code
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ categroy.php?c=$1 [L,QSA]
RewriteRule ^(.*)/(.*)$ single.php?c=$1&name=$2 [L,QSA]
</IfModule>
Each RewriteRule works for its own but together i will not get the expected results.
so i tried it serval days now and i don't get it.
So hope someone here can help
Thanks a lot
There are several issues here with your attempt, but the main point is that you need to take care about the order of your rules. Since rules are applied from top to bottom you need to place more specialized rules first in the file (so further up), more general rules later ...
Here is a modified version to point you into the right direction:
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [END]
RewriteRule ^/?(\w+)/(\w+)/?$ single.php?c=$1&name=$2 [END,QSA]
RewriteRule ^/?(\w+)/?$ category.php?c=$1 [END,QSA]
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.
These rules 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).