iis 7.0 php rewrite,iis7.0 rewrite重写伪静态

This

walkthrough will guide you through how to create and test a set of

rewrite rules for the URL Rewrite Module.

Prerequisites

This walkthrough requires the following prerequisites:

IIS 7 with ASP.NET role service enabled.

URL Rewrite Module Go Live release installed.

Setting up a test Web page

To demonstrate how the URL Rewrite Module works, we will use a

simple test ASP.NET page. This page reads the Web server variables

and outputs their values in the browser.

Copy the following ASP.NET code and put it in the

%SystemDrive%\inetpub\wwwroot\ folder in a file called

article.aspx:

%>

/p>

Transitional//EN"

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

xmlns="http://www.w3.org/1999/xhtml">

URL Rewrite Module

Test

URL Rewrite Module Test

Page

Server Variable	Value
Original URL:	Request.ServerVariables["HTTP_X_ORIGINAL_URL"] %>
Final URL:	Request.ServerVariables["SCRIPT_NAME"] + "?" + Request.ServerVariables["QUERY_STRING"] %>

After copying this file, browse to

http://localhost/article.aspx and check that the

page was rendered correctly in a browser.

Creating a rewrite rule

We will create a simple rewrite rule that rewrites URLs by using

the following format:

http://localhost/article/342/some-article-title

will be rewritten as:

http://localhost/article.aspx?id=342&title=some-article-title.

We will create a rewrite rule by using URL Rewrite UI in IIS

Manager. To do this follow these steps:

Go to IIS Manager.

Select Default Web Site.

In the Feature View click URL Rewrite.

In the Actions pane on right-hand side, click

Add rules…

In the Add Rules dialog box, select the

Blank Rule and click Ok.

Now you must define the actual rewrite rule. In the URL Rewrite

Module, a rewrite rule is defined by specifying four required

pieces of information:

Name of the rule.

Pattern to use for matching the URL string.

Optional set of conditions.

Action to perform if a pattern is matched and whether all

conditions checks succeed.

Naming a rule

In the Name text box, enter a name that will

uniquely identify the rule, for example: ”Rewrite to

article.aspx”.

Defining a pattern

In the Pattern text box, enter the following

string:

^article/([0-9]+)/([_0-9a-z-]+)

This string is a regular expression that specifies that the

pattern will match any URL string that meets the following

conditions:

Starts with the sequence of characters “article/”.

Contains one or more numeric characters after the first

“/”.

Contains one or more alphanumeric or “_” or “-” characters

after the second “/”.

Notice that certain parts of the regular expression are within

parentheses. These parentheses create capture groups, which can be

later referenced in the rule by using back-references.

Defining an action

Since the rule that we are creating is supposed to rewrite the

URL, choose the Rewrite action type that is listed

in the Action group box. In the Rewrite

URL: text box, enter the following string:

article.aspx?id={R:1}&title={R:2}

This string specifies the new value to which the input URL

should be rewritten. Notice that for the values of the query string

parameters we used {R:1} and {R:2}, which are back-references to

the capture groups that were defined in the rule pattern by using

parentheses.

Leave default values for all other settings. The Edit

Rule property page should look like the following

page:

Save the rule by clicking

Apply on the right-hand side.

Viewing the rewrite rule in configuration file

The rewrite rules are stored either in

the ApplicationHost.config file or in Web.config

files. To check the configuration of the rule that we have just

created, open a Web.config file located in

%SystemDrive%\inetput\wwwroot\. In this file you should

see the

section that contains this rule definition:

/>

url="article.aspx?id={R:1}&title={R:2}"

/>

Testing the rule

To test that the rule correctly rewrites URLs, open a Web

browser and request the following URL:

http://localhost/article/234/some-title

You should see that the rewrite rule on

your Web server has changed the original URL to

Article.aspx and it has passed “234” and “some-title” as values for

query string parameters.

Creating a redirect rule

Now we will create a redirect rule that will redirect all URLs

in the following format:

http://localhost/blog/some-other-title/543

will be redirected to:

http://localhost/article/543/some-other-title

To do this, open the URL Rewrite feature view UI in IIS Manager

and then click Add Rule… and then select

the Blank Rule template

again.

Within the Edit Rule page, enter the

following:

Name: Redirect from blog (This is a unique

name for the rule.)

Pattern: ^blog/([_0-9a-z-]+)/([0-9]+) (This

pattern will match the URL string that starts with “blog” and

captures the second and third segments of the URL into

back-references.)

Action: Redirect (The redirect action will

cause a redirect response to be sent back to the browser.)

Redirect URL: article/{R:2}/{R:1} (This

substitution string will be used as a redirect URL; notice that it

uses back-references to preserve and rearrange the original URL

pieces captured during pattern match.)

Leave default values for all other settings. The Edit

Rule property page should look like the following

page:

Save the rule by clicking

Apply on the right-hand side.

Testing the rule

To test that the rule redirects requests correctly, open a Web

browser and request the following URL:

http://localhost/blog/some-other-title/323

You should see that the browser was redirected to

http://localhost/article/323/some-other-title as a

result of redirect rule execution and then the request was

rewritten in accordance to the rewrite rule that you have created

earlier.

Creating an access block rule

The third rule that we will create is used to block all requests

made to a Web site if those requests do not have the host header

set. This type of rule is useful when you want to prevent hacking

attempts that are made by issuing HTTP requests against the IP

address of the server instead of using the host name.

We will create this rule without using IIS Manager. Open the

Web.config file and locate the

section. Insert the

following rule:

negate="true" />

into the collection, so

that it is a first rule in a collection. The

section should look like

the following code:

negate="true" />

/>

redirectType="Found" />

/>

url="article.aspx?id={R:1}&title={R:2}"

/>

Let’s analyze the rule to understand what it does.

url=".*"/> This element says that the rule will match any

URL string.

pattern="localhost" negate="true"

/> This

element adds a condition to the rule that retrieves the host header

value by reading the server variable HTTP_HOST, matches it against

the pattern “localhost” and then negates the result of matching. In

other words, the condition verifies that the host header does not

match “localhost.”

/> This

element tells the URL Rewrite Module to end the HTTP request.

Testing the rule

To test this rule, open a Web browser and make a request to

http://127.0.0.1/article/234/some-title. What you

should see is a browser that does not receive any response from the

server. However, if you request

http://localhost/article/234/some-title, then the

Web server will respond successfully.

Summary

In this walkthrough you have learned how to configure URL

rewrite rules by using IIS manager or by manually editing

Web.config files. The rules that were created in this walkthrough

demonstrated some of the important features of

the URL Rewrite Module, such as regular

expressions support and the ability to use HTTP headers and server

variables to make rewriting decisions.