As per my other question UrlRewriter.NET with .NET 4.0 not working I was unable to get UrlRewriter.NET to work.
So now I have tried ManagedFusion. It works locally but does not work on the server BUT the errors are different and I sense that this might actually work and I have done something wrong in the configuration.
So my web.config settings are (condensed version)
<section name="managedFusion.rewriter" type="ManagedFusion.Rewriter.Configuration.ManagedFusionRewriterSectionGroup"/>
<apache defaultFileName="ManagedFusion.Rewriter.txt" />
<proxy useAsyncProxy="true" />
<identity impersonate="false" />
<add name="RewriterModule" type="ManagedFusion.Rewriter.RewriterModule, ManagedFusion.Rewriter"/>
<validation validateIntegratedModeConfiguration="false" />
<add name="RewriterModule" type="ManagedFusion.Rewriter.RewriterModule, ManagedFusion.Rewriter" />
<add name="RewriterProxyHandler" preCondition="integratedMode" verb="*" path="RewriterProxy.axd" type="System.Web.HttpForbiddenHandler, System.Web, Version=220.127.116.11, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
<defaultDocument enabled="false" />
RewriteRule ^/Campaign/List /Campaign/List.aspx [NC]
Hi this is actually a very common
GoDaddy issue. I am going to post an update to this answer after I review my notes and forums on the
(by the way I am the primary developer of it)
You mind if we take this offline, we need to chat back and forth so I can understand your setup. A quick way as explained in the
readme.txt to trouble shoot problems is to turn on the logging.
RewriteLog /log/log.txt RewriteLogLevel 9
The only problem with
GoDaddy is that you need to create this log directory and give it write permissions, because if I remember right
GoDaddy doesn't allow write permissions in the root.