Comments on: Using IIS URL Rewrite Extensions to Redirect Default.aspx

By: umesh chand

umesh chand — Wed, 23 Jun 2010 11:30:22 +0000

Mr. Ruslan Yakushev solution works but it also creates problem.When i try to login from my default page it doesn’t work even when i use search button on master page it also not working,when i do the same thing from other pages everything works and when i remove that rule from my config then only it works from default page

By: Jacques | SEO Expert

Jacques | SEO Expert — Thu, 29 Oct 2009 08:33:40 +0000

Nothing worse than redirects that gets seen as unique entities, rather than one common page. 1000 links divided by 4 pages suddenly dramatically devalues your offering, making it vulnerable to being eclipsed in search rankings by your competitors. Thanks for the great advice offered here to prevent this guys!

By: Tennerfest

Tennerfest — Wed, 30 Sep 2009 08:05:28 +0000

We definitely went down the IIS7 rewrite module route – however, as Michael points out, the canonical tag is also a good approach to take.

By: Michael

Michael — Sat, 18 Jul 2009 09:30:04 +0000

Hi Barry,

Looks like the canonical url tag will take care of this headache.

By: Learn how to play Las Vegas craps

Learn how to play Las Vegas craps — Thu, 18 Jun 2009 08:29:47 +0000

Hi. Can the IIS7 URL rewriter be used with Cassini server? I imagine not, but I wonder how to incorporate this useful feature into the development process. The Intelligencia offering allows development with Cassini and then deployment to a web server. It would be great to use the new IIS7 version instead.
Thanks!

By: Hotels en Espagne

Hotels en Espagne — Thu, 02 Apr 2009 21:11:34 +0000

Same problem over here with II6 as well. It seems somebody has a solution, I haven’t tried it yet though.. Just wanted to share the info with you and see your replies:

http://swortham.blogspot.com/2008/12/redirecting-default-page-defaultaspx-to.html

By: Cheap Flights Guy

Cheap Flights Guy — Fri, 27 Feb 2009 21:48:25 +0000

Here is the code I was using (converted to vb.net from Mike’s c#)

Dim hostname As String = Request.Url.AbsoluteUri.ToLower
If hostname.EndsWith(“/default.aspx”) Then
sNewURL = Left$(hostname, Len(hostname) – 12)
Response.Redirect(sNewURL, False)
Response.StatusCode = 301
Response.End()
End If

sNewURL is set to the the same URL, but with the default.aspx removed. However, it .Net just adds the default.aspx straight back on. This test was done on my localhost machine, so it might be different on a www. url – but it would be great to have a solution that worked for both.

By: Cheap Flights Guy

Cheap Flights Guy — Fri, 27 Feb 2009 21:45:32 +0000

I tried Mike’s solution – it kept on adding the ‘/default’ to the end of the url & so always ended up in a loop.

By: Louis Gomez

Louis Gomez — Wed, 11 Feb 2009 22:03:27 +0000

Did anyone find a solution to this problem for IIS 6.0? I installed Helicon’s ISAPI filter and the redirect works but it creates issues with my asp.net gridview control. When you select a record, it merely reloads Default.aspx after the postback. Hmm, session state issue??

Louis

By: Scott

Scott — Tue, 13 Jan 2009 22:11:46 +0000

Barry,
Did Mike’s suggestion not work? I checked all of those URL’s and they still stand alone, not redirecting to the preferred domain. Any solution on the endless loop yet when working with IIS 6.0? I have a client in the same boat and he can’t get it figured out. Plus, we’re about to go through a site-wide URL re-write and they’re on IIS 6.0. I’ve seen mixed reviews on the challenges this can present for webmasters vs. IIS 7.