Server Error

Come on, you don't really expect that I can do something about your problem with this amount of information? LOL

Please give me information about your set-up :-)

Sorry..

IIS7 Integrated Pipeline
asp.net 3.5  (umbraco 35 web.config)

Got umbraco 404 redirect working by inserting <httpErrors existingResponse="PassThrough"/> inside <system.webServer>, but it is only working with .aspx files.

301 redirect not is still not working.

I'm trying to redirect old .htm, html, and .php files that no longer exist.

Checked 404handlers.config and the handler is present.

<?xml version="1.0" encoding="utf-8"?>
<NotFoundHandlers>
  <notFound assembly="umbraco" type="SearchForAlias" />
  <notFound assembly="umbraco" type="SearchForTemplate" />
  <notFound assembly="umbraco" type="SearchForProfile" />
  <notFound assembly="InfoCaster.Umbraco._301UrlTracker" type="Handler301URLTracker" />
  <notFound assembly="umbraco" type="handle404" />
</NotFoundHandlers>

Verified that the assembly is in the bin.  OK

Added new property to master document type using 301 Url Tracker datatype.

Added custom mappings to current nodes using old url of .htm, html, and .php files.

HELP!

I have a feeling you need to take a step back, and configure IIS to put all requests through the ASP.NET processor. That's the only way umbraco (and it's extensions) can handle non .aspx URLs.

Google tells me you should check this out: http://learn.iis.net/page.aspx/508/wildcard-script-mapping-and-iis-7-integrated-pipeline/

Jup, it's definately an IIS issue, not Umbraco or 301 URL Tracker related.

You can see the request isn't even hitting Umbraco, because else Umbraco's 404 page would show up.
If you configure IIS the correct way, the request should hit Umbraco and thereby hit the 301 URL Tracker.

Thanks a bunch.. I'll verify that integrated pipeline is working.

Daniel,

If you've got it working, could you post here what you did? At least mark Ben's post as the answer if his suggestion helped you please :-)

Thanks!

Hi,

Having the same problem. Using integrated pipeline. It's working on my .aspx extensions but fail on folders and .asp etc.

So need help on the System.web config.

Thomas   

Did you try the url Ben posted above?

Yes, I tried Bens link.

Its working on .aspx and on folders but not with .asp, .php etc.  

Daniel talks about "Added custom mappings to current nodes using old url of .htm, html, and .php files" do I need to do this?

sry, forget my last post ;-) of course i need to map them 

ok, I got the iis working but need help with the httphandler

My settings:    <add verb="GET, HEAD, POST, DEBUG" path="*.php" validate="false" type="???"/> so need help with the Type

Thomas
         
    

You do not have to add a HttpHandler...

The request should hit ASP.NET/Umbraco and therefore hit the 301 URL Tracker...

Could you try this:
In the <system.webServer>/<handlers> add a handler.
32 bit: Snippet

<add name="Wildcard" path="*" verb="*" type="" modules="IsapiModule" scriptProcessor="%windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll" resourceType="Unspecified" requireAccess="Script" allowPathInfo="false" preCondition="classicMode,runtimeVersionv2.0,bitness32" responseBufferLimit="4194304" />

64 bit: Snippet

<add name="Wildcard" path="*" verb="*" type="" modules="IsapiModule" scriptProcessor="%windir%\Microsoft.NET\Framework64\v2.0.50727\aspnet_isapi.dll" resourceType="Unspecified" requireAccess="Script" allowPathInfo="false" preCondition="classicMode,runtimeVersionv2.0,bitness64" responseBufferLimit="4194304" />

And tell me, is the app pool running in classic mode, or integrated pipeline?

I am Running IIS 6.... on prod. And think it's running in classicMode. My skills on IIS setup are very poor ;-)

It looks like I don't "reach" the handler 

I made the extension in the application mapping to .php. Limit to: GET,HEAD,POST,DEBUG and Verify that files exsits = false

Executable c:\windows\microsoft.net\framework\v2.0.50727\aspnet_isapi.dll

Thomas, did that do the trick or are you still looking for a solution?

This post is about MVC, but is the same issue you're facing, maybe it'll help: http://blog.stevensanderson.com/2008/07/04/options-for-deploying-aspnet-mvc-to-iis-6/

OK, thx. for the link(and help).  I will look into it and keep you updated, for now I use the URLrewriter config file in Umbraco, but love the work you made. Great Package! My company will use it for sure, when it comes out of Beta. (And IIS setup are working)

Let me know have we can contribute to the project.

Thomas

@Thomas

Could you mark the most helpfull reply as 'The answer'? So this topic can be 'closed'? :-)

Doug Mackay had a great suggestion in another topic, will work with .asp too I think:

I've been investigating the issue of getting it to work with .php/.cfm pages :-

I belive that the umbraco 404 handlers only work with .aspx or extensionless url's (this is hard coded into the umbraco requestModule).

As a workaround you can set-up the UrlRewritter to rewrite .php requests to a .aspx page that does't exist :-

<add name="phprewrite"
     virtualUrl="^~/(.*).php"
     rewriteUrlParameter="ExcludeFromClientQueryString"                 
     destinationUrl="~/php/$1.aspx"
     ignoreCase="true" />

This then enables you to use the custom mapping in the 301 URL Tracker

e.g.

Custom mappings :-

/php/oldpage.aspx

/php/olddir/oldpage.aspx

So /oldpage.php or /olddir/oldpage.php will get 301 redirected to the umbraco page that you've set the custom mapping on.

I have just run into this issue and needed to 301 Redirect some old HTML pages. I can confirm that the above solution of rewriting them to aspx file extensions works as intended, it doesn't feel right but it does work. Curious why the Umbraco requestModule would only explicitly handle .aspx or extensionless urls though?

@Simon

I'm not sure wether the umbraco requestModule has something to do with it. My guts tell me the cause is with IIS, which fires the staticFileHandler for html extensions, not the ISAPI module

is working on a reply...