韦伯花园的魔法师 magician in Web 2.0 Party - 外文翻译

美国国务卿克林顿夫人关于互联网自由的讲演

fanxiaojie@yeah.net(fanxiaojie) — Fri,22 Jan 2010 20:24:35 +0800

Remarks on Internet Freedom(关于互联网自由的备忘录)
Hillary Rodham Clinton希拉里·罗德姆·克林顿
Secretary of State国务卿
The Newseum新闻博物馆
Washington, DC华盛顿哥伦比亚特区
January 21, 2010 2010年1月21日

这篇文章太长了,我得慢慢翻译,过几天来看我的博客吧！

如果谁愿意帮我翻译一部分，请将翻译好的内容发邮件到ms.fanxiaojie@163.com

我最近翻译的ServerXmlhttp中文手册

fanxiaojie@yeah.net(fanxiaojie) — Thu,14 Jan 2010 00:54:47 +0800

我最近想翻译四本asp&xml相关的电子手册，分别是以下四本：

http://www.asprain.com/uploadpic/2009-12-28/450150254689.jpg">
http://www.asprain.com/uploadpic/2009-12-28/450467475706.jpg">
http://www.asprain.com/uploadpic/2009-12-28/450811141325.jpg">
http://www.asprain.com/uploadpic/2009-12-28/451019973010.jpg">

其中《ServerXmlhttp中文手册》我已经翻译好了。下载地址是：http://www.asprain.com/uploadfile/2010-1-8/789298634349.chm" target="_blank">http://www.asprain.com/uploadfile/2010-1-8/789298634349.chm

Raphaël js用户手册

fanxiaojie@yeah.net(fanxiaojie) — Mon,15 Jun 2009 00:37:05 +0800

What is it?

Raphaël is a small JavaScript library that should simplify your work with vector graphics on the web. If you want to create your own specific chart or image crop and rotate widget, for example, you can achieve it simply and easily with this library. Raphaël是一个小型的Javascript库，它能够简化你为网页上的矢量图所作的工作。如果你想创建你自己的特定的图表或者图片剪裁和旋转部件，你可以用这个库简单轻松地实现它。

Raphaël uses the SVG W3C Recommendation and VML as a base for creating graphics. This means every graphical object you create is also a DOM object, so you can attach JavaScript event handlers or modify them later. Raphaël’s goal is to provide an adapter that will make drawing vector art compatible cross-browser and easy.
Raphaël使用SVG W3C推荐标准和VML作为创建图形的标准。这意味着你创建的每一个图形对象也是一个DOM对象，因此，您可以附加JavaScript的事件处理程序或以后修改它们。Raphaël的目标是提供一种适配器，使绘画艺术载体轻松做到跨浏览器兼容

Raphaël currently supports Firefox3.0+, Safari 3.0+, Opera 9.5+, Chrome 2.0+ and Internet Explorer 6.0+. Raphaël现在支持Firefox 3.0以上版本，Safari 3.0以上版本, Opera 9.5以上版本 , Chrome 2.0以上版本以及IE6.0以上版本。

How to use it?

Download and include raphael.js into your HTML page, then use it as simple as: 下载并包含raphael.js到你的html页上，然后照样例方式使用它：

// Creates canvas 320 × 200 at 10, 50
var paper = Raphael(10, 50, 320, 200);
// Creates circle at x = 50, y = 40, with radius 10
var circle = paper.circle(50, 40, 10);
// Sets the fill attribute of the circle to red (#f00)
circle.attr("fill", "#f00");
// Sets the stroke attribute of the circle to white (#fff)
circle.attr("stroke", "#fff");

aspEmail组件用户手册

fanxiaojie@yeah.net(fanxiaojie) — Mon,08 Jun 2009 13:49:36 +0800

08/09/2005: AspEmail 5.0.0.4 Service Pack Released 2005年8月9日,AspEmail5.0.0.4 Service Pack发布

Version 5.0.0.4 offers a new method, ValidateAddress, which
performs the syntactic validation of an arbitrary email address.版本5.0.0.4提供了一个新方法,ValidateAddress,它执行任何电子邮箱地址的语法验证.

This version also fixes a bug which caused deferred messages in the queue to be timestamped incorrectly. Now, if the Mail.Timestamp property is used, a queued message's Date: header is set to this property,
not the message creation time.这个版本同时修复了一个错误,这个错误曾造成队列被推迟的消息时间戳记不正确。现在，如果Mail.Timestamp属性被使用了，一个消息队列的时间头将被设置为这个属性，而不是消息创建的时间。

Upgrades are absolutely free for the registered users.升级对注册用户来说是完全免费的。

06/24/2003: AspEmail 5.0 Released 2003年6月24日，AspEmail 5.0发布

AspEmail 5.0 offers a lot of new features you have been asking
for, including full Unicode support and memory attachments. But most importantly,
the new version comes with an all-new message queuing module which
supports up to 64 simultaneous SMTP sessions, logging, CRAM-MD5 and NTLM
authentication methods, automatic bounced-message handling, and much more. ASPEmail 5.0提供了很多被要求的新功能，包括全面支持Unicode编码以及记忆附件。但是更重要的是，这个新版本配备了一个全新的消息队列模块，支持多达64个同时进行的SMTP会话、登录，强制的MD5和NTLM身份验证方法，自动退回消息处理，等等。

For the complete list of new features, see Chapter 1
of the manual. Download AspEmail 5.0 http://www.aspemail.com/download.html" target="_blank">here.
Upgrades are absolutely free for registered users.如要了解完整的新功能，请看手册的第一章。下载aspemail5.0http://www.aspemail.com/download.html" target="_blank">在此。

8/19/2002: .NET Code Samples Added 2002年8月19日加入了.Net例子

Although AspEmail 4.5 is not a native .NET component, it has been
thoroughly tested to work under the ASP.NET environment. We have added
C# versions of all our code samples to the setup.
Download the updated aspemail.exe setup and start taking advantage of AspEmail's unique features under .NET now!虽然aspEmail 4.5.1不是一个自有的.Net组件，但是它已经在asp.net环境下被彻底测试过了。我们已经在所有安装程序的代码试例中加入了C#版本。现在就去下载这个更新的aspemail.exe并开始使用AspEmail在asp.net环境里的独特功能吧！

3/25/2002: AspEmail 4.5.0.2 Service Release Available 2002年3月25日，AspEmail 4.5.0.2Service发布可用了

NEW!Mail.MailFrom property added.
In earlier versions, both the From: and Return-Path: headers were set to the Mail.From value. For bounced-mail handling
purposes, it may be useful to set the Return-Path: header
to an email address other than the sender's address, and that's what the MailFrom property does.新特色：加入了Mail.MailFrom属性。在早期的版本中，From和Return-Path头都被设置为Mail.From的值。对于退回的邮件的处理目的，给邮件的地址中加设置一个Return-Path头可能比发送者的地址更有用。这就是MailFrom属性的用处。

NEW!
An optional AddToBody flag added to the AppendBodyFromFile
method to specify whether the Body or AltBody
property should be appended. In earlier versions,
only Body could be appended via this method but not AltBody.新功能：一个可选的AddToBody标识加到AppendBodyFromFile方法中来指定Body或者AltBody属性必须被附上。在早期的版本中，只有Body能够被通过这个方法附加，但是AltBody不能。

NEW!
For better compliance with the SMTP protocol,
AspEmail 4.5.0.2 issues the command EHLO instead of HELO
whenever the Username property is used.新功能：为了更好地符合SMTP协议，当Username属性被用到的时候，AspEmail4.5.0.2使用EHLO命令来代码HELO命令。

1/24/2001: AspEmail 4.5 Released with multipart/alternative Support 2001年1月24日：AspEmail 4.5发布了多重/替代支持。

With AspEmail 4.5, you can specify a text version of your message along with the HTML version to support email clients that are not HTML-enabled. The HTML part
is still set via the Body property.
The text part is specified via the new property AltBody, as follows:使用AspEmail4.5，你能够给你的已有html版的邮件指定一个文字版，来应对邮件客户端不支持html的功能。html部分依然通过Body属性来设置。文字部分通过这个新属性AltBody来设置，如下所示。

Mail.Body = "<HTML><BODY>Dear Sir:<P>...</HTML>"

Mail.AltBody = "Dear Sir:" & chr(13) & chr(10) & ...

In Version 4.5, SMTP authentication
via the Username and Password properties
is extended to NNTP as well, so you can now use the method
SendToNewsgroup to post articles
to password-protected news servers.在4.5版本中，SMTP通过Username和Password属性认证的功能被扩展到NNTP协议，这样你现在可以使用这个方法SendToNewsgroup来发送文件琶密码保护的服务里了。

AspEmail 4.5
also offers a new property, Timeout,
through which socket timeout values can be set.
在AspEmail 4.5中还提供了一个新属性Timeout，通过这个属性可以设置代理超时时限。

Encryption and Digital Signature Support加密和数字签名支持

AspEmail can be used in conjuncation with AspEncrypt 2.0, our powerful cryptographic component, to send signed messages, encrypted messages, and messages that are first signed and then encrypted, in the S/MIME format. aspEmail能够与我们的强大的加密组件AspEncrypt2.0合起来用，来发送签名消息、加密邮件，以及用S/MIME格式第一次签名再加密的邮件。

Visit http://www.aspencrypt.com">www.aspencrypt.com
to download your free 30-day trial copy of this component.访问www.aspencrypt.com来下载你的30天试用的这个组件的副本。

Send Email from your ASP or VB application with AspEmail 4.5. It's Free!通过你的Asp或者VB应用程序使用AspEmail 4.5发送邮件是免费的！

AspEmail 4.5 is a free active server component that enables your ASP application to send email messages via any external SMTP server. The component supports multiple file attachments, multiple recipients, CCs, BCCs, and REPLY-TOs. AspEmail 4.5是一个免费的Active Server组件，使您的ASP应用程序通过任何外部SMTP服务器发送电子邮件信息。该组件支持多种文件附件，多个收件人、CCs、BCCs以及回复邮件。

In addition to basic functionality available for free, AspEmail 4.5 offers a number of premium features
that require a registration key after a 30-day evaluation period. These features are support for message queuing, embedded images, Quoted-Printable format,
multipart/alternative support and authentication.
Regular file attachments are still free, of course.除了基全的免费功能提供，AspEmail4。5在30天评估期之后还提供了一些高级功能，但是使用它需要一个注册码。这些功能支持消息队列、嵌入式图像引用、打印格式、多重/替代的支持和验证。当然，常规文件附件仍然免费。

Spice up Your Messages with Embedded Images and Sounds在你的邮件里嵌入图像和声音。

This premium feature allows you to send messages in the HTML format
with embedded images and backgrounds. You can even embed
sounds in your messages. Here is how it's done:这个溢价功能允许你在用html格式发送消息时同时带上嵌入式图像和背景。你甚至可以在你的消息里嵌入声音，这里有个做法示例

...

Mail.AddEmbeddedImage "c:\dir\bk.gif", "My-Image"

Mail.Body = _

"<HTML><BODY BACKGROUND=""cid:My-Image"">...</HTML>"

or或者

Mail.AddEmbeddedImage "c:\dir\ring.wav", "My-Sound"

Mail.Body = _

"<HTML><BGSOUND SRC=""cid:My-Sound""></BGSOUND>..."

Send Messages with File Attachments over the Web.通过网络发送带附件的消息。

AspEmail can be used in conjunction with AspUpload, the leading file upload component
from http://www.persits.com">Persits Software, to sendmessages with file attachments over the Web,
as demonstrated by our Live Demo. aspEmail还能够与领先的文件上传组件aspUpload合用(从Persits Software下载这个组件)，从而通过网络发送带文件附件的消息，就像我们现场演示的那样。

最近准备翻译一部swift 3D的教程

fanxiaojie@yeah.net(fanxiaojie) — Sat,23 May 2009 09:25:00 +0800

之前很想学swift3D,但是网上的中文教程真是一点都找不到.就算有,也非常简陋,一点都不详细.后来我发现其实最详细的教程就在眼皮底下.那个软件自带的那本userGuider.pdf写得非常详细.可惜是英文版的.这本教程有两百多页,我打算把它翻译成中文.因为时间关系,我只选择重要的部分翻译,不重要的部分就算了.希望我的心血能够对想学习这款软件的人有帮助.

下面将是连载:

ISAPI_Rewrite用户手册11

fanxiaojie@yeah.net(fanxiaojie) — Fri,24 Apr 2009 11:22:04 +0800

RewriteMap directive

Description:	Defines a key to value mapping function
Syntax:	RewriteMap MapName MapType:MapSource
Context:	server config, virtual host, directory, .htaccess

RewriteMap directive is used to define a key-to-value lookup function.
  This is useful when you need to map large amount of values since it is much
  faster than doing it with rule matching. Performance of map function rely on
  a size of map file insignificantly. There are three types of mapping:

txt: mapping using text file map;

rnd: random value select from multiple choices;

int: internal functions.

MapName is the name of mapping function that will
  be used to refer to this map from RewriteRule command. Make sure that every
  mapping is defined with a unique name. You can call mapping function in the
  Susbtitution value of RewriteRule directive using the following syntax:

${ MapName : LookupKey | DefaultValue }

If this construction is found in Substitution, ISAPI_Rewrite will lookup
  for the key in the map and if one is found, substitute the construct by its value.
  If no key is found, optional DefaultValue will be used. If no DefaultValue
  is specified, it will be substituted by an empty string.

Here is an example of declaring maps:

RewriteMap examplemap txt:C:/path/to/file/map.txt

Path to MapSource file coule be either absolute or relative. Relative
path are calculeted from the folder with current configuration file, i.e. from
the configuration file path where this map has been declared.

Then you may use this map in RewriteRule as follows:

RewriteRule ^/ex/(.*) ${examplemap:$1}

The following combinations for MapType and MapSource can
be used:

txt: Plain text mapping. The source is a Windows
file system path to a valid text file. Text file should be of the following
format:

#This is a comment



    key1 value1 #Another comment

    key2 value2

    keyN valueN

rnd: Random multiple values lookup. Source is the path to a text
file of the following format:

#This is a comment



    key1 value1|value2|value3

    key2 value4|value5|value6|valueN

int: Internal function call. Source should be one of the following
pre-defined internal functions:

toupper: Converts the key to all upper case.

tolower: Converts the key to all lower case.

escape: Encode special characters to hex values.

unescape: Unencode hex values to special characters.

RewriteMap directive

Description:	Defines a key to value mapping function
Syntax:	RewriteMap MapName MapType:MapSource
Context:	server config, virtual host, directory, .htaccess

txt: mapping using text file map;

rnd: random value select from multiple choices;

int: internal functions.

${ MapName : LookupKey | DefaultValue }

Here is an example of declaring maps:

RewriteMap examplemap txt:C:/path/to/file/map.txt

Then you may use this map in RewriteRule as follows:

RewriteRule ^/ex/(.*) ${examplemap:$1}

The following combinations for MapType and MapSource can
be used:

txt: Plain text mapping. The source is a Windows
file system path to a valid text file. Text file should be of the following
format:

#This is a comment



    key1 value1 #Another comment

    key2 value2

    keyN valueN

rnd: Random multiple values lookup. Source is the path to a text
file of the following format:

#This is a comment



    key1 value1|value2|value3

    key2 value4|value5|value6|valueN

int: Internal function call. Source should be one of the following
pre-defined internal functions:

toupper: Converts the key to all upper case.

tolower: Converts the key to all lower case.

escape: Encode special characters to hex values.

unescape: Unencode hex values to special characters.

RewriteLogLevel directive

Description:	Sets the level of logging
Syntax:	RewriteLogLevel Level
Default:	RewriteLogLevel 0
Context:	server config

This directive sets the verbosity of logging output. The default value of 0
means no logging while maximum level of 9 means all actions will be logged.

Using higher values of logging may slow down ISAPI_Rewrite operation. We recommend
you to disable logging by setting log level to 0 after debugging of your ruleset
has been completed.

ISAPI_Rewrite用户手册10

fanxiaojie@yeah.net(fanxiaojie) — Wed,22 Apr 2009 11:11:41 +0800

RewriteProxy directive

Description:	Proxy request to a distant server
Syntax:	RewriteProxy Pattern Substitution [flags]
Context:	server config, virtual host, directory, .htaccess

Causes the resulting URL to be internally treated as a target on another server and immediately (i.e. rules processing stops here) passed to the remote server. Response of the remote server will then be passed back to the client. Proxy requires you to specify fully qualified URL, starting from protocol, host name, etc. ISAPI_Rewrite uses ISAPI extension to handle proxy requests. You can read more about this in configuring proxy chapter.

Syntax and operation is the same as for RewriteRule directive, but RewriteProxy directive supports some additional flags:

H (preserve Host)

Proxy module will use Host header sent in original request when connecting to remote server. Without this flag proxy will compose Host header from a host name and a port of a remote server.

A (Add authentication headers)

Allows passing of an authentication information from proxy to an internal server when client authentication against a proxy server is used. Proxy module will append headers

X-ISRW-Proxy-AUTH-TYPE,
X-ISRW-Proxy-AUTH-USER,
X-ISRW-Proxy-LOGON-USER,
X-ISRW-Proxy-REMOTE-USER

corresponding to server variables

AUTH_TYPE,
AUTH_USER,
LOGON_USER,
REMOTE_USER

to a request sent to a proxied server.

CR (use Credentials)

Proxy module will try to login on a remote server with the credentials specified in the URL or basic authentication headers. With this flag you can use http://user:password@host.com/path/ syntax as a URL within substitution string.

RewriteProxy directive

Description:	Proxy request to a distant server
Syntax:	RewriteProxy Pattern Substitution [flags]
Context:	server config, virtual host, directory, .htaccess

Syntax and operation is the same as for RewriteRule directive, but RewriteProxy directive supports some additional flags:

H (preserve Host)

Proxy module will use Host header sent in original request when connecting to remote server. Without this flag proxy will compose Host header from a host name and a port of a remote server.

A (Add authentication headers)

Allows passing of an authentication information from proxy to an internal server when client authentication against a proxy server is used. Proxy module will append headers

X-ISRW-Proxy-AUTH-TYPE,
X-ISRW-Proxy-AUTH-USER,
X-ISRW-Proxy-LOGON-USER,
X-ISRW-Proxy-REMOTE-USER

corresponding to server variables

AUTH_TYPE,
AUTH_USER,
LOGON_USER,
REMOTE_USER

to a request sent to a proxied server.

CR (use Credentials)

Proxy module will try to login on a remote server with the credentials specified in the URL or basic authentication headers. With this flag you can use http://user:password@host.com/path/ syntax as a URL within substitution string.

RewriteHeader directive

Description:	Rewrites any HTTP header in request
Syntax:	RewriteHeader HeaderName: Pattern Substitution [flags]
Context:	server config, virtual host, directory, .htaccess

The RewriteHeader directive is more general variant of RewriteRule directive and it is designed to rewrite not only the URL part of client request, but any HTTP header. Technically RewriteRule directive is equivalent to the RewriteHeader URL Pattern Substitution [flags]. This directive can be used to rewrite, create or delete any HTTP headers in the client request before it will be processed by further applications on IIS.

HeaderName: specifies name of HTTP header that will be rewritten.

Pattern, Substitution and flags are the same as for RewriteRule directive.

ISAPI_Rewrite用户手册09

fanxiaojie@yeah.net(fanxiaojie) — Mon,20 Apr 2009 10:57:56 +0800

RewriteCond directive

Description:	Defines a condition for the following RewriteRule
Syntax:	RewriteCond TestString CondPattern
Context:	server config, virtual host, directory, .htaccess

This directive defines a single condition for the following RewriteRule,
  RewriteHeader or RewriteProxy directive. There can be one
  or more conditions preceding a rule directive and the rule will only apply
  if all of the conditions are met.

TestString additionally to plain text can contain
the following constructs:

Back references to RewriteRule pattern using syntax $N.

Back references to preceding RewriteCond patterns using syntax
%N.

RewriteMap expansions using syntax ${mapname:key|default}.

HTTP header value with the syntax %{HTTP:header}.

Server variable using the syntax %{ NAME_OF_VARIABLE }.

    Here is a list of available server variables:|

HTTP_USER_AGENT

            HTTP_REFERER

            HTTP_COOKIE

            HTTP_FORWARDED

            HTTP_HOST

            HTTP_PROXY_CONNECTION

            HTTP_ACCEPT



            REMOTE_ADDR

            REMOTE_HOST

            REMOTE_PORT

            REMOTE_USER

            REMOTE_IDENT

            REQUEST_METHOD

            SCRIPT_FILENAME

            PATH_INFO

            QUERY_STRING

            AUTH_TYPE

DOCUMENT_ROOT

            SERVER_NAME

            SERVER_ADDR

            SERVER_PORT

            SERVER_PROTOCOL

            SERVER_SOFTWARE



            API_VERSION

            THE_REQUEST

            REQUEST_URI

            REQUEST_FILENAME

            HTTPS

TIME_YEAR

            TIME_MON

            TIME_DAY

            TIME_HOUR

            TIME_MIN

            TIME_SEC

            TIME_WDAY

            TIME

Additionally all specail IIS server variables are supported.

CondPattern specifies a regular expression that will
be applied to the instance of TestString. Following special values are also
supported:

Prefix regular expression with '!' symbol to specify negation
pattern.

'<CondPattern' Treats CondPattern as a plain
string that will be lexicographically compared as more than.

'>CondPattern' Lexicographically less then comparison.

'=CondPattern' Lexicographically equals comparison.

'-d' Test string is existing directory.

'-f' Test string is existing file.

'-s' Test string is a file with nonzero size.

'-l' (link) Unsupported, always false.

'-x' (has executable permissions) Unsupported, always
true.

'-F' (is existing file, via subrequest) Unsupported, same
as '–f'.

'-U' (is existing URL, via subrequest) Unsupported, always
false.

The following flags are also supported:

'nocase|NC'



    This flag makes the Pattern case-insensitive.

'ornext|OR'



    This flag combines subsequent RewriteCond directives with logical or instead
    of implicit AND.

O



    Leaved for compatibility with ISAPI_Rewrite 2.x. Normalizes string before
    processing. Normalization includes removing of an URL-encoding, illegal characters,
    etc. Also, IIS normalization of a URL completely removes query string from
    it.

ISAPI_Rewrite用户手册08

fanxiaojie@yeah.net(fanxiaojie) — Sat,18 Apr 2009 19:42:56 +0800

RewriteRule directive

Description:	Defines URL rewriting rule
Syntax:	RewriteRule Pattern Substitution [flags]
Context:	server config, virtual host, directory, .htaccess

This directive defines a single URL rewriting operation. It may occur more
  that once in configuration file with each instance defining a rule to rewrite
  URL. RewriteRule directive consists of URL matching Pattern, Substitution string
  and optional set of flags.

Pattern is a perl compatible regular expression which
  will be matched against current URL. The current URL can be originally requested
  URL or URL already altered by preceding rules. URL never includes protocol or
  host name and starts from the first slash character (true for httpd.conf only).
  Also current URL differs depending on a level of configuration that is applied,
  i.e. for directory level configuration (.htaccess file) trailing slash and configuration
  file directory name will be omitted from the URL to match against. Please see
  Regular expression syntax section of the documentation
  for more information on building regular expressions.

Preceding pattern by a '!' character will negate entire expression. Negated
pattern cannot generate submatches so you cannot use $N references in substitution.

Substitution string specifies format string to generate
new URL if the Pattern was matched. In addition to plain text, it can
include these specail characters:

back references to RewriteRule pattern $N

back references to RewriteCond patterns %N

server variables %{VARNAME}

conditional format patterns ?Ntrue_string:false_string

grouping parenthesis ‘(‘ and ‘)’

Substitution strings treat all characters as literals except for '$', '\',
  '(', ')', '?', ':' and '\'. To read special characters literally it is recommended
  to escape it with '\'. The following special characters are
  allowed:

$&	Outputs what matched the whole expression.
$`	Outputs the text between the end of the last match found (or the start of the text if no previous match was found), and the start of the current match.
$'	Outputs all the text following the end of the current match.
$$	Outputs a literal '$'
\a	The bell character.
\f	The form feed character.
\n	The newline character.
\r	The carriage return character.
\t	The tab character.
\v	A vertical tab character.
\x	A hexadecimal character - for example \x0D.
\x{}	A possible unicode hexadecimal character - for example \x{1A0}
\cx	The ASCII escape character x, for example \c@ is equivalent to escape-@.
\e	The ASCII escape character.
\dd	An octal character constant, for example \10.
\l	Causes the next character to be outputted, to be output in lower case.
\u	Causes the next character to be outputted, to be output in upper case.
\L	Causes all subsequent characters to be output in lower case, until a \E is found.
\U	Causes all subsequent characters to be output in upper case, until a \E is found.
\E	Terminates a \L or \U sequence.
\\	Single back slash character '\'

RewriteRules are applied in the order of appearance in configuration file, starting
  from the parent configuration files. Each rule will apply only if its
  Pattern matches a URL and all connected conditions (RewriteCond) are
  also matched. After that URL is completely replaced by a Substitution
  and rewriting process continues until the end of configuration file or a rule
  with any of the stop flags. Special string '-' (dash) in Substitution
  means no substitution, and it is useful when you need to apply the rule while leaving
  original URL untouched.

Additionally here is the list of supported flags that
  can alter rule behavior. Fully Apache compatible flags are marked green,
  unsupported flags are red, and additional flags only
  supported by ISAPI_Rewrite are yellow. ISAPI_Rewrite
  will ignore all unsupported flags.

CU (Case Upper)



    Changes the case of substitution result to upper.

CL (Case Lower)



    Changes the case of substitution result to lower.

chain|C



    Chains current rule with the next rule. Next rule will be executed only if
    current rule is matched. Chain can be subsequent.

cookie|CO=NAME:VAL:domain[:lifetime[:path]]



    Sets a cookie header with the fields specified and send it to the client with
    the response to the current request.

env|E=VAR:VAL



    Unsupported. In UNIX environment sets an environment variable. Meaningless
    for Windows systems.

forbidden|F



    Sends immediate 403 FORBIDDEN response to the client. Stops rule processing
    and all other subsequent processing on this request.

gone|G



    Sends immediate 401 GONE response to the client. Stops rule processing and
    all other subsequent processing on this request.

handler|H=Content-handler



    Unsupported. Explicitly specifies handler for a request. In IIS world this
    can be achieved by rewriting file extension of requested file but there is
    no direct translation from Apache handlers to IIS file extensions.

last|L



    Stops rewrite process here and doesn’t apply any more rules from the current
    configuration file. Descendant .htaccess files will still be applied if any.

loop|LP



    Re-runs current single rule in the loop while it’s pattern and conditions
    are matched. Number of iterations is limited to a value of 200 to avoid infinite
    loops.

next|N



    Re-runs rewriting process starting from the beginning of current configuration
    file. Number of iterations is limited to a value of 200 to avoid infinite
    loops.

nocase|NC



    This flag makes the Pattern case-insensitive.

noescape|NE



    Don't escape output. By default ISAPI_Rewrite will encode all non-ANSI characters
    as %xx hex codes in output.

nosubreq|NS



    ISAPI_Rewrite meaning of this flag differs from Apache. Exact translation
    isn't possible, but this flag may still be useful. Every time when configuration
    file processing has been finished and URL has been rewritten, ISAPI_Rewrite
    will start processing with this new URL again (same as Apache) making it possible
    to apply another configuration file. This flag means that the rule should
    be executed only for initial user request and not for rewritten requests,
    to prevent possible loops. ISAPI_Rewrite limits number of loops to 10 repetitions.

O (nOrmalize)



    Leaved for compatibility with ISAPI_Rewrite 2.x. If RewriteCompatibility2
    on is used, this directive normalizes URL before processing. Normalization
    includes removing of an URL-encoding, illegal characters, etc. Also normalization
    of URL completely removes query string from it. If no RewriteCompatibility2
    on is used, URLs are normilized by default (as it is done in mod_rewrite)
    and meaning of this flag is inverted.

proxy|P



    Forces the resulting URL to be internally treated as a target on another server
    and immediately (i.e. rules processing stops here) passed to the remote server.
    Response of the remote server will then be passed back to the client. Proxy
    requires you to specify fully qualified URL, starting from protocol, host
    name, etc. ISAPI_Rewrite uses ISAPI extension to handle proxy requests. You
    can read more about this in configuring proxy chapter.

passthrough|PT



    Unsupported or always on. Result is always passed through the next handler
    in IIS.

qsappend|QSA



    Appends current query string data to a substitution string instead of replacing
    it by a substitution. Use this when you need to add more query string parameters
    while preserving original parameters.

redirect|R [=code]



    Forces server to send immediate response to client with redirect instruction,
    providing Substitution as a new location. It can optionally prefix Substitution
    with http://thishost[:thisport]/ bringing URL to a valid absolute form. If
    no code is given, a HTTP response of 302 (MOVED TEMPORARILY) will be used.
    You can optionally specify any code from 3xx range.

skip|S=num



    Forces the rewriting engine to skip the next num rules in sequence,
    if the current rule matches.

type|T=MIME-type



    Forces the MIME-type of the target file to be MIME-type. This can be used to
    set up the content-type based on some conditions.

U (Unmangle
    log)



    Unmangle log. Log the URL as it was originally requested and not as the URL
    was rewritten.

ISAPI_Rewrite用户手册07

fanxiaojie@yeah.net(fanxiaojie) — Thu,16 Apr 2009 10:42:26 +0800

AccessFileName directive 获得文件名指令

Description描述:	Sets name of distributed configuration file分布式配置文件的集名称
Syntax语法:	AccessFileName filename [filename] ...
Default默认:	AccessFileName .htaccess
Context上下文:	server config

Specifies a list of file names that ISAPI_Rewrite will look for distributed
  configurations. Default file name is .htaccess. ISAPI_Rewrite will only load
  the first found file in this list. By default ISAPI_Rewrite Manager will mark configuration
  files with hidden attribute - this will prevent the file from being
  requested directly by a remote user.在特定文件名列表中ISAPI_Rewrite将寻找分布式配置。默认的文件名是.htaccess。ISAPI_Rewrite将只载入列表中第一个找到的文件。默认情况下ISAPI_Rewrite将把配置文件的属性标记为隐藏——这将保护文件不受远程用户的修改请求。

When any changes are applied to the configuration file it will be reloaded automatically upon the next request to the server.当配置文件发生任何变化时，它将在下一次请求服务器时自动重载入。

AllowOverride directive 允许覆盖指令

Description描述:	Explicitly sets the base URL for per-directory rewrites.为每个目录重写明确规定基准网址。
Syntax语法:	AllowOverride All\|None\|directive-type [directive-type] ...
Default默认:	AllowOverride All
Context上下文:	server config, virtual host, directory

This directive decalres which directives in distributed .htaccess
  files can override directives from the parent levels (httpd.conf).
  In context of ISAPI_Rewrite this directive in fact enables or disables .htaccess
  files for specific virtual host (web site) or directory. Only three values are currently
  supported: All, None and FileInfo.本指令声明了在分布式.htAccess文件中的指令是否能覆盖父层中指令(httpd.conf)。在ISAPI_Rewrite背景下这个指令实际上为特定虚拟主机或者目录启用或者禁用了.htaccess文件。只有三个值目前是被支持的：All、None和FileInfo。

All and FileInfo enables .htaccess file and
  all ISAPI_Rewrite directives in it. None disables all .htaccess
  files and directives. This directive is inheritable. This means if you specify
  AllowOverride none for some directory or virtual host .htaccess files
  will also be disabled for all subdirectories.All和FileInfo激活了.htaccess文件和它里面所有的ISAPI_Rewrite指令。None禁用了所有.htaccess文件和指令。这个指令是具有继承性的，这意味着如果你为一些目录或虚拟主机指定AllowOverride none，.htaccess文件也将在所有子目录里被禁用。

RewriteEngine directive重写引擎指令

Description描述:	Enables or disables runtime rewriting engine启用或者禁用运行时的重写引擎
Syntax语法:	RewriteEngine on\|off
Default默认:	RewriteEngine off
Context上下文:	server config, virtual host, directory, .htaccess

Enables or disables rewriting runtime. Use RewriteEngine off instead of commenting
out rewrite rules if you need to disable ISAPI_Rewrite module or specific .htaccess
file.启用或者禁用重写运行时。当你需要让ISAPI_Rewrite模式失效或者特定的.htaccess失效时，用重写引擎关闭来代替注释掉rewrite规则

WARNING! Due to the number of support
  queries we had to enable rewriting engine by default whilst in Apache rewriting
  engine by default is off. Please keep in mind this small incompatibility and
  always specify explicit status of rewriting engine in each configuration file,
  whether you need it on or off.警告：由于支持查询的数量，我们在不得不启用重写引擎的情况下，Apache rewriteing引擎必须被关掉。请记住这个小小的不相容，并在所有的配置文件中始终指定明确的rewrite引擎状态：你需要关闭它还是打开它。