IIS7 remove file extension

iisiis-7rewrite

I'm trying to configure IIS7 (Windows Server 2008) so that I can use URL's that do not include the file extension (i.e. somepage.php would become http://DOMAIN/somepage)

I'm using the URL rewrite tool in IIS7, and have the following rule:

Match URL

Requested URL - Matches the pattern

Using: Wildcards

Pattern: /*

No conditions.

Action

Action Type: Rewrite

Action properties - Rewrite URL: {R:1}.php, append query string

It's returning a 404 error. When I use the Test Pattern tool, it appears to work, and R:1 is what I want to add before the file extension. Any help or ideas would be greatly appreciated!

Thanks!

Best Answer

You need to change the rule to use regular expressions instead of wildcards. This is because the R:1 is a regexp backreference.

Also - you probably want your pattern to be (.*) for it to be R:1 (most likely it will be R:0 without the parens - R:0 is the backreference for "the entire match")

Check out http://learn.iis.net/page.aspx/497/user-friendly-url---rule-template/ for lots of info on the user friendly URL portion of URL Rewrite.

Related Solutions

IIS6 vs. IIS7 and IIS7.5: handling URLs with plus sign (+) in base (not querystring)

After searching for more combinations of IIS and plus, it appears that IIS7[.5] is set up to reject URLs with a plus sign by default out of some fear of the use of that character; that symbol is still allowed in the querystring, though. The solution is to alter the requestFiltering attribute default on <system><webServer><security><requestFiltering> to allow doubly-encoded characters with a command line call (ultimately modifying your ASP.NET web.config):

%windir%\system32\inetsrv\appcmd set config "Default Web Site" -section:system.webServer/security/requestFiltering -allowDoubleEscaping:true

This may be a bit more dangerous than one prefers to be with their web site, but there didn't appear to be a way to be more specific than a blanket allow. The warnings were regarding the mismatching that could occur between using a plus in a URL and its typical translation as a space. It looks like the only other alternative is to stop using plus characters in your URLs at all.

IIS 7 URL rewrite rule

A rewrite needs to be a relative path on disk, under the same website. That's what is causing the 404 error in your case.

A redirect will send a client-side redirect, but that won't work since 192.168.1.11 is an internal IP that can't be accessed publicly.

What you need is ARR: http://www.iis.net/expand/ApplicationRequestRouting. It's a reverse proxy and will take the public request and forward it on to the internal server. This is the middle man between the client and the internal server. It leverages IIS and URL Rewrite so you're already much of the way there.

Best Answer

Related Solutions

IIS6 vs. IIS7 and IIS7.5: handling URLs with plus sign (+) in base (not querystring)

IIS 7 URL rewrite rule

Related Topic