url-rewriting

问题 When I enter the website.com/seo link, I want to make a 301 redirect to the website.com/seo/ link. However, I don't want it to be broken in the codes I wrote in the current htaccess. my htacces codes: RewriteEngine On RewriteBase / RewriteCond %{THE_REQUEST} ^[A-Z]{3,}\s([^.]+)\.php [NC] RewriteRule ^ %1/ [R=301,L] RewriteCond %{REQUEST_FILENAME} !-d RewriteCond %{REQUEST_FILENAME}.php -f RewriteRule ^(.*?)/?$ $1.php [NC,L] 回答1: Use only one of these, do not use together! Try: RewriteEngine

问题 I want to redirect example.com/?lang=en to example.com/en/ . I am using Python Django and my server running Plesk / Nginx. I try to redirect on my webpage like this. But it's don't work; rewrite ^/?lang=en$ /en/ redirect; But if i remove question mark rewrite is worked. I tried many methods but I couldn't find a solution. Thank You. 回答1: The most simple is if ($arg_lang = en) { return 301 /en$uri; } However if you'd have any other query arguments, they would lost with this redirection rule.

问题 I want to redirect example.com/?lang=en to example.com/en/ . I am using Python Django and my server running Plesk / Nginx. I try to redirect on my webpage like this. But it's don't work; rewrite ^/?lang=en$ /en/ redirect; But if i remove question mark rewrite is worked. I tried many methods but I couldn't find a solution. Thank You. 回答1: The most simple is if ($arg_lang = en) { return 301 /en$uri; } However if you'd have any other query arguments, they would lost with this redirection rule.

问题 I'm running Joomla 2.5 on an IIS7 server. The problem is Joomla's search engine friendly urls don't work. Whatever url I enter, it goes to index.php. After a painful day of struggling with rewrite rules and IIS settings, I came to two realizations: Search engine friendly urls are only broken when the urls are unicode. In my WAMP server, on which the SEF urls work perfectly: $_SERVER['REQUEST_URI'] is "mydomain/%D9%85%D8%AD%D8%B5%D9%88%D9%84%D8%A7%D8%AA/%D9%82%D9%84%D8%A8%DB%8C-%D8%B9%D8%B1%D9

问题 I'm trying to make a rewrite rule in Nginx, that contains "?amp" at the end of the request, like this: From http://mywebsite.com/path1/lalala?amp To http://mywebsite.com/path1/lalala It's a redirect 301. I tried some rules, but they do not work, I get many redirects (looping). Examples that did not work. rewrite ^/path1/lalala.*? htttp://mywebsite.com/path1/lalala? permanent; Or rewrite ^/path1/lalala.*? /path1/lalala? permanent; I think the problem is in the query string "?amp". Do you know

问题 I'm running into some problems with rewriting my URLs. Recently moved to a new host where FollowSymLinks and SymLinksIfOwnersMatch is not allowed as options in my .htaccess file. Using these will give me a 500 error. Mod_rewrite is however enabled on the host. Normally my rewriting code looks like the code below and works perfectly: Options +FollowSymLinks RewriteEngine on RewriteRule ^link/(.*)$ link.php?urlkey=$1 [QSA] But with removing +FollowSymLinks the rewriting doesn't work. Any idea

问题 I'm running into some problems with rewriting my URLs. Recently moved to a new host where FollowSymLinks and SymLinksIfOwnersMatch is not allowed as options in my .htaccess file. Using these will give me a 500 error. Mod_rewrite is however enabled on the host. Normally my rewriting code looks like the code below and works perfectly: Options +FollowSymLinks RewriteEngine on RewriteRule ^link/(.*)$ link.php?urlkey=$1 [QSA] But with removing +FollowSymLinks the rewriting doesn't work. Any idea

问题 I'd plastered all over the Internet that this code in your .htaccess file will remove the file ending: RewriteEngine on RewriteCond %{REQUEST_FILENAME} !-d RewriteCond %{REQUEST_FILENAME}\.php -f RewriteRule ^(.*)$ $1.php However, although enables the URL without file ending, it does not disable the URL with file ending. Essentially, what I'd like to force any attempt for an request with file ending (domain.com/sample.php) to end up without file ending (domain.com/sample) I'm sure someone

问题 I am currently using the following rules in a .htaccess file: RewriteEngine on RewriteCond %{REQUEST_FILENAME} !-d RewriteCond %{REQUEST_FILENAME}\.php -f RewriteRule ^(.*)$ $1.php This works well to ensure that /myfile.php works as well as just myfile (with no extension in the URL). It also handles querystrings with no problems, so myfile?var=foo also works. The problem is that these are registering in Google Analytics as being two separate files. So while myfile.php might be the third most

问题 I am currently using the following rules in a .htaccess file: RewriteEngine on RewriteCond %{REQUEST_FILENAME} !-d RewriteCond %{REQUEST_FILENAME}\.php -f RewriteRule ^(.*)$ $1.php This works well to ensure that /myfile.php works as well as just myfile (with no extension in the URL). It also handles querystrings with no problems, so myfile?var=foo also works. The problem is that these are registering in Google Analytics as being two separate files. So while myfile.php might be the third most