简体   繁体   English

.htaccess url 重写以从 url 中删除操作名称

[英].htaccess url rewriting to remove action names from urls

I have my urls like this我有这样的网址

domain.com/index.php?id=126&action=Category&name=Vegetables domain.com/index.php?id=126&action=Category&name=蔬菜

I want my urls to look like this我希望我的网址看起来像这样

domain.com/126/Category/Vegetables domain.com/126/Category/蔬菜

I have tried a lot using .htaccess but could not able to do.我已经尝试了很多使用 .htaccess 但做不到。

Your help and suggestion required.需要您的帮助和建议。

Sounds pretty straight forward:听起来很简单:

RewriteEngine on
RewriteRule ^/?(\d+)/([^/]+)/([^/]+)$ /index.php?id=$1&action=$2&name=$3 [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.如果您使用上述规则收到内部服务器错误(http 状态 500),那么您很可能操作的是非常旧版本的 apache http 服务器。 You will see a definite hint to an unsupported [END] flag in your http servers error log file in that case.在这种情况下,您将在 http 服务器错误日志文件中看到不支持的[END]标志的明确提示。 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.您可以尝试升级或使用旧的[L]标志,在这种情况下它可能会起作用,尽管这取决于您的设置。

This implementation will work likewise in the http servers host configuration or inside a distributed configuration file (".htaccess" file).此实现同样适用于 http 服务器主机配置或分布式配置文件(“.htaccess”文件)中。 Obviously the rewriting module needs to be loaded inside the http server and enabled in the http host.显然重写模块需要在 http 服务器内部加载并在 http 主机中启用。 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.如果您使用分布式配置文件,您需要注意它的解释在主机配置中完全启用,并且它位于主机的DOCUMENT_ROOT文件夹中。

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").和一般性评论:您应该始终更喜欢将此类规则放在 http 服务器主机配置中,而不是使用分布式配置文件(“.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.这些分布式配置文件增加了复杂性,通常是意外行为的原因,难以调试,它们确实减慢了 http 服务器的速度。 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).它们仅在您无法访问真正的 http 服务器主机配置(阅读:非常便宜的服务提供商)或坚持编写自己的规则的应用程序(这是一个明显的安全噩梦)的情况下作为最后一个选项提供。

 <IfModule mod_rewrite.c> RewriteEngine On RewriteCond %{REQUEST_FILENAME}.-d RewriteRule ^(,*)/$ /$1 [LR] RewriteCond %{THE_REQUEST} \ /(?*/|)(:.index\?php)?\?name=([^\s&]+) [NC] RewriteRule ^ /%1%2/, [R=302,L.NE] RewriteCond %{REQUEST_FILENAME}.-f RewriteCond %{REQUEST_FILENAME}.-d RewriteCond %{REQUEST_URI}?index\.php RewriteRule ^(:*/|)([^/]*)$ $1index,php,name=$2/ [L] RewriteEngine On RewriteCond %{HTTPS};=on RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301,NE] Header always set Content-Security-Policy "upgrade-insecure-requests;" </IfModule>

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM