In a previous post I have outlined problems with the umbraco backend.
I have just restored the test site from backup to V3.0.3
IIS 6 with multiple umbraco databases, all working fine on ASP.NET 2 (3.0.3, 4.x and 4.5.2) They all share a common thread pool named umbracoCMSAppPool
I have created a NEW database with its OWN thread pool named umbracoCMSAppPool_V4 so that I can isolate any issues with the testing site or application.
I have a strange issue:
umbraco 3.0.3 using ASP.NET 2.x server.site.com/umbraco works as expected and allows me to login to the back office.
Switching the ASP.NET model to 4.x and restarting the thread pool and IIS and clearing the browser cache server.site.com/umbraco returns a page not found? Instead I must type: server.site.com/umbraco/
Why is the SAME umbraco install (v3.0.3) unable to handle the url without the closing slash properly in ASP.NET v4. Is this an umbraco bug or asp.net 4 bug?
I ask because one I upgrae the site to 4.5.2 and ASP.NET 4 this problem is amplified and I can not get the back office to work properly. The 4.5.1 site using ASP.NET 2 (in the other thread pool) works just fine.
No... like most things umbraco, getting an asnwer is at the whim of how the community feels and what other topics are popular. It is bothersome, but most would argue that there is an eay workaround so it is not important.
You could take the time to post it to codeplex, but your vote and my vote will likely be the only ones and therefore it would not get attention either.
This lead me to see that in IIS Web Service Extensions section ASP.Net 4.0 was not enabled so I enabled it
I have a Win Server 2003 64bit VPS and had two versions of the .Net framework installed 64 and 32 bit, it loooked like the 32bit was regsistered so I registered the 64 bit framework
I enabled wildcard mapping on the ASP.Net 4.0 sites I was having trouble with and everything started working
+1 for the feedback on the issue, I'm sure you've spent quite some time finding the cause, and think it's fabulous you're sharing the solution with the community. Thanks again.
I've always had that issue with the /umbraco folder, from 4.0 and upwards (didn't get into Umbraco until then, so don't have a 3.x site to compare to). Anything without a / is treated as content by Umbraco (so it throws a 404 because it can't find a node called /umbraco), and anything with a / on the end is treated like a folder (I think, I've not grubbed around in the core to check).
One easy way round this is to add a rewrite rule in the rewriting config file to permanently redirect /umbraco to /umbraco/.
Problems with ASP.NET 4.x and /umbraco
In a previous post I have outlined problems with the umbraco backend.
I have just restored the test site from backup to V3.0.3
IIS 6 with multiple umbraco databases, all working fine on ASP.NET 2 (3.0.3, 4.x and 4.5.2) They all share a common thread pool named umbracoCMSAppPool
I have created a NEW database with its OWN thread pool named umbracoCMSAppPool_V4 so that I can isolate any issues with the testing site or application.
I have a strange issue:
umbraco 3.0.3 using ASP.NET 2.x
server.site.com/umbraco
works as expected and allows me to login to the back office.
Switching the ASP.NET model to 4.x and restarting the thread pool and IIS and clearing the browser cache
server.site.com/umbraco
returns a page not found?
Instead I must type:
server.site.com/umbraco/
Why is the SAME umbraco install (v3.0.3) unable to handle the url without the closing slash properly in ASP.NET v4. Is this an umbraco bug or asp.net 4 bug?
I ask because one I upgrae the site to 4.5.2 and ASP.NET 4 this problem is amplified and I can not get the back office to work properly. The 4.5.1 site using ASP.NET 2 (in the other thread pool) works just fine.
It seems to be an IIS/ASP.NET thing. An explanation about trailing slashes can be found here: http://danielmiessler.com/study/hyperlink_trailing_slash/
hth, Thomas
Thanks for the link Thomas, interesting though in my case it is not "slow" due to added requestes, it just does not work.
To recap SAME umbraco site:
ASP.NET 2.x
domain.com/umbraco
Gets me into the umbraco back office
ASP.NET 4.x
domain.com/umbraco
Results in "page not found"
Is this the behavior the rest of you are seeing with ASP.NET 4 enabled?
Does anybody else have any thoughts on this or the ability to confirm the behavior I am seeing?
I am getting a 404 a swell on ASP.Net 4.0 did you ever get a fix for this?
No... like most things umbraco, getting an asnwer is at the whim of how the community feels and what other topics are popular. It is bothersome, but most would argue that there is an eay workaround so it is not important.
You could take the time to post it to codeplex, but your vote and my vote will likely be the only ones and therefore it would not get attention either.
I fixed my issue I was having. I tracked it down to not being Umbraco but .Net 4.0, here is how I worked it out:
2010-09-25 21:08:32 W3SVC812548228 88.80.197.187 GET / - 85 - 94.193.138.209 Mozilla/5.0+(Windows;+U;+Windows+NT+6.1;+en-GB;+rv:1.9.2.10)+Gecko/20100914+Firefox/3.6.10 404 2 1260
I hope this helps you.
Brendan,
+1 for the feedback on the issue, I'm sure you've spent quite some time finding the cause, and think it's fabulous you're sharing the solution with the community. Thanks again.
Cheers,
/Dirk
Thanks Dirk, it was a bit of a treasure hunt to track it down but I got there :)
Hi William,
I've always had that issue with the /umbraco folder, from 4.0 and upwards (didn't get into Umbraco until then, so don't have a 3.x site to compare to). Anything without a / is treated as content by Umbraco (so it throws a 404 because it can't find a node called /umbraco), and anything with a / on the end is treated like a folder (I think, I've not grubbed around in the core to check).
One easy way round this is to add a rewrite rule in the rewriting config file to permanently redirect /umbraco to /umbraco/.
Hope that helps!
Cheers,
Tim.
is working on a reply...