Description of ISAPI Rewrite Rules

Source: Internet
Author: User

I (ignore case)
This flag affects the rewriterule command and the corresponding rewritecond command regardless of case.
F (Forbidden)
Respond to the client, stop the rewriting process, and send the 403 error. Note that in this case, formatstring is useless and can be set to any non-null string.
L (last rule)
Stop the rewrite process here without applying any rewrite rules. Use this flag to prevent the currently overwritten URI from being overwritten again by the subsequent rules.
N (next iteration)
Force rewritingengine to adjust the rule target and restart the rule from scratch (all modifications will be saved). The number of reboots is limited by the value specified by repeatlimit. If this value exceeds n flag, it will be ignored.
NS (Next iteration of the same rule)
Restart the rule process (for example, force repeated rule application) from the same rule with N, and use the repeatlimit command to specify the maximum number of rules that are repeatedly implemented,
P (Force proxy)
Force the target URI to be a proxy internally and immediately scale up to cope with proxy requirements through ISAPI. Make sure that the proxy string is a valid Uri, including the Protocol host, or else the proxy will return an error.
R (explicit redirect)
Forces the server to send a redirection to the client to immediately respond and provide a new address of the destination URI. The redirection rule is often the final rule.
RP (permanent redirect)
Almost the same as the [R] flag, but the 301http status is released instead of the 302http status. Code
U (unmangle log)
Uri is recorded when the URI is a source requirement rather than a rewrite Requirement
O (normalize)
Standardize the string before implementation. Standardization includes URL-ENCODING, invalid character re-movement, etc. This tag is useful for URLs and URLS-ENDODED Headers
CL (case lower)
Lowercase
Cu (Case upper)
Uppercase
Rewriteheader Directive
Syntax: rewriteheader headername pattern formatstring [flags]
This command is a more general variant of rewriterule. It not only overrides the client requirement of the URL, but also overwrites the HTTP header. This command is not only used for rewriting. Generate, delete any HTTP headers, and even change the client request Method
Headername
Specifies the customer header to be overwritten. The value is the same as the testverb parameter in the rewritecond command.
Pattern
Restrict rule expressions to match request-Uri,
Formatstring
Specify the formatstring of the new Uri.
[Flags]
Is a command separation list of the following flags
I (ignore case)
This flag affects the rewriterule command and the corresponding rewritecond command regardless of case.
F (Forbidden)
Respond to the client, stop the rewriting process, and send the 403 error. Note that in this case, formatstring is useless and can be set to any non-null string.
L (last rule)
Stop the rewrite process here without applying any rewrite rules. Use this flag to prevent the currently overwritten URI from being overwritten again by the subsequent rules.
N (next iteration)
Force rewritingengine to adjust the rule target and restart the rule from scratch (all modifications will be saved). The number of reboots is limited by the value specified by repeatlimit. If this value exceeds n flag, it will be ignored.
NS (Next iteration of the same rule)
Restart the rule process (for example, force repeated rule application) from the same rule with N, and use the repeatlimit command to specify the maximum number of rules that are repeatedly implemented,
R (explicit redirect)
Forces the server to send a redirection to the client to immediately respond and provide a new address of the destination URI. The redirection rule is often the final rule.
RP (permanent redirect)
It is almost the same as the [R] flag, but the 301http status code is released instead of the 302http status code.
U (unmangle log)
Uri is recorded when the URI is a source requirement rather than a rewrite Requirement
O (normalize)
Standardize the string before implementation. Standardization includes URL-ENCODING, invalid character re-movement, etc. This tag is useful for URLs and URLS-ENDODED Headers
CL (case lower)
Lowercase
Cu (Case upper)
Uppercase

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.