Search results matching tag 'URL Rewrite Module'

Rewrite Subdomain to Subfolder (possible bug)

MV2001 — Tue, 10 Nov 2009 13:53:57 GMT

Hello all:

My domain "just4test.com" has a Static/Permanent IP associated (w.x.y.z) and a DNS Zone record like this...

* A w.x.y.z

... so that when you write on a browser "any_subdomain".just4test.com you are redirected to the main IP Domain.

Examples:
user1.just4test.com --> w.x.y.z
user2.just4test.com --> w.x.y.z
userN.just4test.com --> w.x.y.z

I've created a IIS7 URL Rewrite Rule, with this objective:

userN.just4test.com/folder --(rewrite URL to)--> userN.just4test.com/userN/folder

This is running properly like this...

userN.just4test.com --(rewriting URL to)--> userN.just4test.com/userN/Default.aspx

and like this...

userN.just4test.com/ts/ --(rewriting URL to)--> userN.just4test.com/userN/ts/Default.aspx

BUT IT'S NOT RUNNING LIKE THIS...

userN.just4test.com/ts --(rewriting URL to)--> userN.just4test.com/userN/userN/ts/Default.aspx

For some strange reason that I don't reach to understand, the subdomain is converted to a folder path TWICE.

This is the URL Rewrite Rule that I'm applying:

<rule name="subdomain.domain.com/whatever -> subdomain.domain.com/subdomain/whatever" enabled="true" stopProcessing="true">
   <match url="(.*)" />
      <conditions logicalGrouping="MatchAll">
         <add input="{HTTP_HOST}" negate="true" pattern="^www\.just4test\.com$" />
         <add input="{HTTP_HOST}" pattern="^(\w+)\.just4test\.com$" />
      </conditions>
   <action type="Rewrite" url="{C:1}/{R:1}" appendQueryString="true" />
</rule>

FINAL NOTES:

- My Default.aspx is a test web page created as explained here, in order to see the HTTP_X_ORIGINAL_URL and SCRIPT_NAME variables.

- There is a Default.aspx page on wwwroot, on wwwroot/userN and on wwwroot/userN/ts folders. And YES, they are all REAL folders, not VIRTUAL folders.

- I've used the Failed Request Tracing to Trace Rewrite Rules, and the only contribution is to know that the URL Rewrite module is receiving the URL as this...

userN.just4test.com/userN/ts

...when no RULE should still been applied.

THANKS.

Implementing the Default Document rule using the URL Rewrite Module

will1968 — Thu, 05 Nov 2009 12:59:44 GMT

I tried to implemented the Default redirect rule but the default.aspx (in the root folder of my site) page seem to postback onto itself when i click on an asp button or link button.

I don't have a problem with a standard href link which successfully allows me to navigate to a new page.

This is what I have for the url rewrite in the webconfig.....

<rule name="Default Document" stopProcessing="true">
<match url="(.*)default.aspx" />
<action type="Redirect" url="{R:1}" redirectType="Permanent" />
</rule>

taken from http://blogs.msdn.com/carlosag/archi...commentmessage

The code that should run and take me to a new page is this...

Protected Sub cmdShoppingBasket_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles cmdShoppingBasket.Click
Response.Redirect("~/Shopping-Basket.aspx")
End Sub

The code does a few other things as well before the response.redirect.

The site is hosted on discountasp.net.

Thanks

Will

Convert Drupal Boost Module Rules

mikeytown2 — Sun, 25 Oct 2009 01:33:07 GMT

Wondering if IIS7 can handle the required rules of the Boost module. I was at the Pacific Northwest Drupal Summit today & this is a concern of mine.

Redirect causing Application Pool freeze

bdun — Sun, 11 Oct 2009 23:45:06 GMT

I have 4 Rewrite rules trying to handle friendly URL's for a site but when they are enabled, the site eventually becomes unresponsive. If I manually recycle the app pool it starts up again.

I have enabled FRT on the Urlrewrite module but don't really know what I need to be looking for that might be causing this.

The server has 3.5 SP1 with the URLrewrite 1.1 module installed.

There is a classic asp app running in a virtual directory in the root which may be related.

Here are the rules. I have tried various alterations to conditions but this is the current state they are at (with enabled="true" when turned on obviously)

Why are my relative paths different when I request the file name opposed to directory?

mcdotnet — Thu, 08 Oct 2009 11:46:14 GMT

I am rewriting the url http://www.tworiverstaines.co.uk to http://www.tworiverstaines.co.uk/TwoRivers/ using this rule:
               <rule name="tworiverstaines.co.uk" stopProcessing="false">
                    <match url="(.*)" />
                    <conditions logicalGrouping="MatchAll">
                        <add input="{PATH_INFO}" negate="true" pattern="^.?TwoRivers/.*" />
                        <add input="{HTTP_HOST}" pattern="^www.tworiverstaines.co.uk$" />
                    </conditions>
                    <action type="Rewrite" url="TwoRivers/{PATH_INFO}" />
                </rule>

I am using the tilde ~ in all the relative links for my web controls.

When I navigate to http://www.tworiverstaines.co.uk/ all the paths in the default document are:
href="Filename.aspx" which is what I want.

When I navigate directly to the file http://www.tworiverstaines.co.uk/Default.aspx all the paths are: href="TwoRivers/Filename.aspx" which results in the subfolder being shown in the browser address bar when clicking this link, which I do not want.

Does anyone know why the paths change?

Re: Rewriting Extensionless URLs

devgineer — Thu, 08 Oct 2009 07:33:42 GMT

Thanks Ruslan,

That link was exactly what I needed for the query string problem. As for the session, the anchored regex pattern didn't help. This is what my redirect looks like now.
<rule name="Redirect aspx to extensionless" stopProcessing="true">
<match url="(.*)\.aspx$" />
<action type="Redirect" url="{R:1}" redirectType="Permanent" />
</rule>

I tried removing the stopProcessing attribute, and also removing and adding session back in the modules collection via this recommendation http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=357248
Here is the post that lead me to that bug on Microsoft Connect
http://forums.iis.net/t/1151614.aspx

I've tried putting my 'rewrite' collection before and after the 'modules' collection. None of these help with the session. Here is my modlues collection.
    <modules runAllManagedModulesForAllRequests="true">
      <remove name="ScriptModule"/>
      <add name="ScriptModule" preCondition="managedHandler" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<remove name="Session" />
<add name="Session" type="System.Web.SessionState.SessionStateModule" preCondition="" />
    </modules>

As for cookies, I am not using cookieless sessions. Right now this is on a staging site on a subdomain and the www redirect rule is not in web.config so the cookie's shouldn't be getting lost through the redirection. I am completely lost as to why the session isn't working based on other posts/workarounds I have worked and tried.

Re: Rewriting Extensionless URLs

devgineer — Wed, 07 Oct 2009 08:03:11 GMT

Does anybody know why the redirects break the session state? If I remove all the redirect rules I can use session state if I go directly to an extensionless url. So if I type in www.mydomain.com/directory/file the session state works fine and the url gets correctly rewritten. If I put in the redirect rules and go to www.mydomain.com/directory/file.aspx it get's redirected to www.mydomain.com/directory/file and rewritten fine but my session does not work. I've already added the runAllManagedModulesForAllRequests="true" attritbute to the modules element web.config and it doesn't make a difference. Any pointers would be greatly appreciated.

Very strange URL rewrite problem?

mcdotnet — Mon, 05 Oct 2009 10:42:36 GMT

I am rewriting the url http://www.tworiverstaines.co.uk to http://www.tworiverstaines.co.uk/TwoRivers/ using this rule:
<match url="(.*)" />
<conditions logicalGrouping="MatchAny">
<add input="{HTTP_HOST}" pattern="^www.tworiverstaines.co.uk$" />
</conditions>
<action type="Rewrite" url="TwoRivers/{PATH_INFO}" />

When the site first loads the rewrite works correctly displaying Default.aspx with all the hyperlinks working correctly including the path to the App_Themes folder etc.

However when you click on the homepage link (or any other) when the Default.aspx (or page requested) loads all the hyperlinks and paths are altered from /Default.aspx to /TwoRivers/Default.aspx so when you click on a hyperlink it is broken as the rewrite rule will take you to www.tworiverstaines.co.uk/TwoRivers/TwoRivers/Default.aspx.

To prevent the 404 error I have added a local rule to rewrite /TwoRivers/TwoRivers/ to /TwoRivers/ however this isn't a good solution as the URL in the browser shows the subfolder and pages become available at /Default.aspx and /TwoRivers/Default.aspx which could present duplicate content issues with search engines.

Does anyone have any idea why this is happening?

The site can be accessed at http://www.tworiverstaines.co.uk

I am displaying the header information at the bottom of each page to display the paths. The web server is running IIS 7 ASP.NET 3.5 SP1.

Re: Rewriting the home page

devgineer — Sat, 03 Oct 2009 18:14:02 GMT

Are you redirecting your documents to extensionless? I'm asking because you have '^about' instead of 'about.aspx', you could try using the following for your 'Rewrite home page' rule.
<match url="/default" ignoreCase="true" />
or
<match url="/default.aspx" ignoreCase="true" />
depending on whether you are using extensions or not. For my site I redirect *.aspx to extensionless, redirect '/default' to '/' Then rewrite the extensionless documents back to .aspx. Documents that requested the default document i.e '/' get rewritten to 'default.aspx'. You can take a look at my post here

http://forums.iis.net/t/1161355.aspx

IIS 7.0 URL Rewrite and SharePoint 2007

Robyn_Hutton — Tue, 08 Sep 2009 14:30:00 GMT

I was wondering if anyone has had any experience (and hopefully some success) using the IIS 7.0 URL Rewrite module with SharePoint 2007.

My fear is that SharePoint is not going to allow the IIS 7.0 URL Rewrite module to handle redirects.

I added a URL Rewrite wildcard rule against my SharePoint development environment, but it is as if the rule is being ignored completely and I am getting the standard SharePoint 404 NOT FOUND error.

Is there anybody who has had success using these two technologies together?