Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Dropping the .aspx extension for vanity URLsDropping the .aspx extension for vanity URLs
Previous
 
Next
New Post
4/9/2012 7:37 PM
 

Why does this work?

I'm using DNN 6.1.5 and I wanted to create vanity URLs for Landing Pages off the main menu. I created pages not on the menu but at the top menu level. It worked great, even with re-direction to the actual target page. However on one site I was able to drop the .aspx extension and it still worked. On newer sites, I would get a 404 error, page not found.

After checking the web.config files I found that the site that allow me to drop the .aspx did not have the ManagedHandler precondition for the URL Rewrite module. Once I removed it, I was able to use http://mysite.com/landingpage without the .aspx. This is the line in the web.config:

<add name="UrlRewrite" type="DotNetNuke.HttpModules.UrlRewriteModule, DotNetNuke.HttpModules" preCondition="managedHandler" />

I just removed the  preCondition="managedHandler"   from that item and it worked.

On the older site that gave me this idea, it was also running 6.1.5, but had been upgraded each release from 4.9. On the new site, it had started as a 6.0 site and had preCondition="managedHandler" on all the add modules. I did a little research and found that this is new with IIS 7.0. On http://blogs.iis.net/thomad/archive/2... they say:

Handlers and Modules can now be written in managed code and directly integrated into the IIS request pipeline. But switching between managed and native code is an expensive operation. The managedHandler precondition was introduced to allow optimizing the performance of requests where no managed code needs to be involved, for example when static files (.html, .jpg etc.) are served. No managed code is called if the request is served by a native handler and every managed module is configured with the managedHandler precondition.

So, this seems to be an efficiency thing. These sites a relatively low traffic, so I think this will work fine. However, I am wondering what the expert community thinks about this, and am also wondering why taking out the preCondition allows the URL Rewriter to work with no .aspx extension, while putting in the preCondition makes it not work. Is there a native URL Rewriter? Care to shed any light? Thanks.

 

 
New Post
4/11/2012 10:29 AM
 

Hi Thomas,

You should have a look at the URL Master by iFinity if you need really clean urls!

Gilles


We (team members) are Humans offering their knowledge, their work and their spare time FOR FREE to benefit the community. It would be so particularly appreciated that your messages begin with "Hello" and end with "Thank you" or any other form of politeness. Ask yourself what your reaction would be, if you were approached by me (a total stranger) on the street to ask you something without saying "Hello" nor "Thank you"? After several years of services dedicated to the community, I begin to be tired to read requests without any form of politeness.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Dropping the .aspx extension for vanity URLsDropping the .aspx extension for vanity URLs


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out