这些重写规则将从头到尾进行计算。
最后一行是实际的重写规则。
这些重写规则表明了正则表达式的功能。
These rewriting rules demonstrate the power of regular expressions.
url重写规则的类型。
每条指令定义单独的重写规则。
配置http重写规则登出到未受保护的url。
Configure HTTP rewrite rules to log out to an unprotected uri.
那里也有一些相对于首页的重写规则。
There is also a rewrite rule for the home page (nothing after the blog URL).
在这里添加重写规则。
一个常见错误是忘了启用用于重写规则的模块。
One common mistake is to forget to enable the module for rewrite rules. Before you can use the rewrite rules, you must uncomment this line.
重写规则可以使用正则表达式来实现功能强大的重写规则。
The rewriting rules can use regular expressions to allow for powerful rewriting rules.
您也可以在子类中重写规则函数，从子类中调用重写的父类函数。
You can also override regular functions in a subclass and call the overridden parent function from within the subclass.
为什么这是[l]国旗未能阻止下重写规则的应用吗？
Why is this [l] flag failing to prevent application of the next rewrite rule?
与此相反的重写规则，我们将采用一个特定的重写战略的共同使用模式。
In contrast to the common usage pattern of rewrite rules we will employ a specific rewriting strategy.
用线性式对这种组合模式进行重写并把它称作短语结构规则或重写规则。
Phrase structural rules: The combinational pattern in a linear formula may be called a phrase structural rule or rewrite rule.
但在使用正则表达式时，重写规则的真正功能才会发挥更大作用，本部分将对此进行探讨。
The true power of the rewriting rules, though, shines when using regular expressions, as we'll see in this section.
我们可以在Web.config文件中使用以下URL重写规则来实现此功能。
We can accomplish this with the following URL rewriting rule in the Web.config file
创建目录和Default .aspx文件后，请继续操作，并向元素中添加以下重写规则。
After creating the directory and Default.aspx file, go ahead and add the following rewriting rule to the element.
前一部分中介绍的简单URL重写显示了如何轻松地为 URL 重写引擎配置新的重写规则。
The simple URL rewriting demonstrated in the previous section showed how easily the URL rewriting engine can be configured with new rewriting rules.
你需要在你的插件初始化的时候做这些事情，以保证这些重写规则在足够早的时候被更新。
You'll need to do this in your plugin's init action, so that it happens early enough in the process.
使用url重写引擎的ASP.NET页面开发人员可以在Web. config文件中指定重写规则。
The ASP.NET page developer utilizing the URL rewriting engine can specify the rewriting rules in the Web.config file.
与 /Products/Beverages.aspx 相似，下面我们要为其他产品类别添加重写规则。
Similar to /Products/Beverages.aspx, we'd next add rewriting rules for the other product categories.
在此处停止重写过程并不再应用任何重写规则。使用此标志以防止当前重写的URI被后续规则再次重写。
Stop the rewriting process here and don't apply any more rewriting rules. Use this flag to prevent the currently rewritten URI from being rewritten further by following rules.
一些已经为你提供好了的重写规则和超过40000个词分类词词典数据库，提供目前科技进步水平重写引擎。
Some well thought rewriting rules and a thesaurus database of more than 40000 words, provide the state of the art rewriting engine.
在这种方法中，您可以创建多个url重写规则，其中每一个都负责将转换一个不同操作的SOAPAction报头。
In this solution, you can create multiple URL-rewrite rules, each one responsible for transforming the SOAPAction header for a different operation.
我们并不取决于多台服务器，甚至还没想过重写规则，但是我们确实需要多数据库系统，你的解决办法比他正准备实施的是要简单点。
We are not up to multiple servers or even thinking of rewrite rules yet, but we do need to have multiple dbs and your solution is slightly simpler than the one he was going to implement.
不像框架(比如mod_python)，使您将应用程序安装在Apache提供的URL上，CherryPy通过重写规则而连接到Apache上。
Unlike frameworks like mod_python that make you mount applications onto URLs served by Apache, CherryPy connects to Apache through rewrite rules.
然后，它将遍历重写规则，每次遍历一个，对于每个规则，它将获取规则的LookFor属性，并使用正则表达式来确定是否在被请求的URL中找到了匹配的规则。
It then iterates through the rewrite rules one at a time, and for each rule, it grabs its LookFor property and USES a regular expression to determine if a match is found in the requested URL.
上面规则的使用都比较可疑,因为他们都可以通过不使用任何替换操作符来重写.
The use of the above rules is questionable, as they all could be rewritten without using any substitution operators.
我们是否在玩一场所有规则都在被不断重写的游戏？
Are we playing in a game where all the rules are constantly being rewritten?
然后，重写阶段应用在这两个昵称上定义的信息约束规则。
The rewrite phase then applies the informational constraint rules that were defined on the two nicknames.
应用推荐