Well, I'm getting more reports like yours lately (since version 1.2). I will look into this soon. Maybe this week, but I'm afraid it will be next week.

I'll keep you posted.

Edit: You know what? I'll look into this tonight :-)

Hi Kipusoep,

Thanks for your support, I have notifications set to on in this thread.

Owen

owen... not related to 301, but did you know that you can, via a couple of settings, have extensionless urls with umbraco???

like /register

there is a post here that references the web.config update required...

http://our.umbraco.org/forum/using/ui-questions/6515-Search-engine-friendly-URLs

hope that helps

Hi Bob,

Yes, I would usually use Directory URLs for this site, however my Client is using shared hosting account without a Dedicated Application Pool, so turning on Directory URL's is causing some problems.

Thanks for your advice,

Owen

Could you post a screenshot of the 404 you're getting?

Hi,

Here is the backend shot:

And the 404:

Seems like this is not a 301 URL Tracker issue.

As you described above, you had problems getting Directory Url's to work. That issue is the same issue as you are experiencing with the 301 URL Tracker. Directory Url's aren't mapped to the ASP.NET ISAPI handler, so the 301 URL Tracker isn't even being called. I can tell this, because you would see umbraco's 404 page if the 301 URL Tracker kicked in and didn't find anything.

Hi,

Ok I am going to try again on a different installation to see if I can get this working, I will post back in a few minutes for an update.

Curious, does this package work if I don't have DirectoryURLS turned on?

Thanks,

Owen

Hi!

Success! I went and installed this on my live setup and it worked! There must be something wrong with development environment!

Thanks again, and sorry for misleading you! 

Owen!

No problem, you just pushed me to write a big notice et the top of the package's description :-)
There's nothing 'wrong' with the development environment, it's just not configured correctly for your needs ;-)

Btw, could you mark this thread as solved? Thanks.

Haha I am glad that you have found useful information in my problem!

I am currently implementing your package again into another site and once again having some problems. The file extension is .asp from the old site and in IIS i know where I select the executable but which one should I choose?

Thanks again!

Owen

This sounds like it could be interesting to read for you...

I went ahead and changed the .asp handler to use aspnet_isapi.dll

I also went and added the handler in the local web.config like so:

 <!-- ASP -->

      <add path="*.asp" verb="*" type="System.Web.UI.PageHandlerFactory" validate="true"/>

    </httpHandlers>

    <compilation defaultLanguage="c#" debug="false" batch="false">

      <buildProviders>

       <add extension=".asp" type="System.Web.Compilation.PageBuildProvider"/>

      </buildProviders>

And now I have a different 404 page when I try /business_solutions.asp:

Stumped!

Thanks,

Owen

I'm not sure if the web.config changes are needed.
The request is hitting ASP.NET now, but it's handled as classic asp page, which is not okay...
Try playing with removing those web.config changes.

Hi,

Removed the changes from the web.config and the 404 page went away, however it is now just replaced with plain blank white screen. No errors on the page.

Feel like im getting closer! Any idea whats up?

Thanks in advance,

Owen

You could use Firebug or Fiddler to inspect what HTTP Status code you're getting.
Anyway, it's still not ok, but I can't help you any further. This is beyond ASP.NET and umbraco, it's really server configuration/IIS.

is working on a reply...