Hi to any on the core team:

I'm noticing that browsing to www.DotNetNuke.com is "hanging" in Google's Chrome with a message "Waiting for cache..." in the bottom left. At the same time, if you browse www.DotNetNuke.com/default.aspx with the same browser (different tab), it's coming up fine (I'm posting this from that tab now).

Is anyone else experiencing this??

Hi Sebastian,

I'm not sure which kind of performance issues you're mentioning, but today when I'm checking it out, it's happening again. It looks like a caching issue of some kind. The performance is perfect when I specify the page as default.aspx, but it still hangs when I'm specifying it as the plain old domain name.

It's almost like the domain isn't resolving to the default page by IIS (where www.TheDomain.com defaults to www.TheDomain.com/default.aspx).

[Edit by="Dan"]
Is this related in any way to the "User's Online Caching Issue"?
[/Edit]

Hi Sebastian,

It turns out that this seems to be a problem in Google's Chrome.

I'm not sure why it was only affecting my browsing of DotNetNuke, but it might be related to the fact that I had Chrome open for a few days as I've been doing some research. It could be that the cached page in Chrome was lost for the basic url whereas the url specifying the "defaut.aspx" was working fine.

I double-checked the behaviour in Chrome, after reading your post, and the problem persisted. Then I cleared Chrome's cache - and the problem still persisted. Finally, I closed all my Chrome windows (about 8 windows with a total around 100 pages), and now www.DotNetNuke.com comes in strong and clear.

I'm not sure why it was a problem only with the browsing og DotNetNuke, except to say that DNN is on my Chrome home page (of most visited), so maybe there is a caching issue around that.

Thanks for your time!