I'm migrating a Umbraco 4.5.2 site from IIS 6 (Windows Server 2003) to IIS 8 (Windows Server 2012). It's working fine (thanks to the forum help) but now backend only enters if type ending slash:
Yes, "/umbraco" would not be a directory. It would be a page. Only "/umbraco/" would be considered a directory. Umbraco should be redirecting from /umbraco to /umbraco/. Not sure why that's not happening.
Alternatively, you could try creating a redirect yourself so that /umbraco redirects to /umbraco/ (you should be able to do that in "/config/UrlRewriting.config").
It's something about ASP.NET framework 4.0, because it also occurs with IIS 6 if I change to this ASP.NET version.
As you suggested, made my own redirect. Didn't get with UrlRewriting.config (maybe I missed something). I made the redirect in a macro at the 404 configured page.
Backend url in IIS 8
Hi.
I'm migrating a Umbraco 4.5.2 site from IIS 6 (Windows Server 2003) to IIS 8 (Windows Server 2012). It's working fine (thanks to the forum help) but now backend only enters if type ending slash:
Works: http://mysyte/umbraco/
Doesn't work (http 404): http://mysite/umbraco
IIS default page is default.aspx.
Changed some configurations in IIS and web.config without success. Has anyone had this problem?
Maybe you need to enable extensionless URL's? http://love2dev.com/#!article/Enable-Extensionless-Urls-in-IIS-7-0-amp-7-5
Hi Nicholas.
This feature is already installed:
Looks like IIS thinks "/umbraco" is not a directory, and doesn't bring the default document (default.aspx).
Yes, "/umbraco" would not be a directory. It would be a page. Only "/umbraco/" would be considered a directory. Umbraco should be redirecting from /umbraco to /umbraco/. Not sure why that's not happening.
Here's something else you can try: http://stackoverflow.com/questions/11325584/asp-net-v4-extensionless-url-feature-does-not-work-on-iis-6-0
Alternatively, you could try creating a redirect yourself so that /umbraco redirects to /umbraco/ (you should be able to do that in "/config/UrlRewriting.config").
Hi Nicholas.
It's something about ASP.NET framework 4.0, because it also occurs with IIS 6 if I change to this ASP.NET version.
As you suggested, made my own redirect. Didn't get with UrlRewriting.config (maybe I missed something). I made the redirect in a macro at the 404 configured page.
Thank you!
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.