I think maybe changing the web.config caused a clearing of all cache and started the humanfriednly url..
I have this on my dev website ..
I have this on my dev website ..
<httpRuntime shutdownTimeout="520" executionTimeout="1900" useFullyQualifiedRedirectUrl="true" maxRequestLength="1228800" requestLengthDiskThreshold="1228800" requestValidationMode="2.0" requestPathInvalidCharacters="<,>,*,%,:,\,?" />
And it's working fine. So I think it was the urlrewriter,, you can test that by moving back to advanced (If you dare!!! :-) ) My thought is that the advanced option should never have been made the default! For 95% of clients the humanfriendly is OK, it's over zealous SEO bods that make the advanced option a must for the Evoq platform....testing it out on the DNN platform might seem the right business thing to do for DNN, but it's a pain in the butt!