My site was apparently rebuilt by my web host today.  After some source-code hacker intrusion, the web host appears to have restored my site from a previous backup.  Now, when a visitor visits the site and has "Warn me when web sites try to redirect or reload the page" checked in FireFox, the warning is triggered when the user visits the site.  This was NOT happening before the rebuild.  Any ideas as to what could be triggering this warning now?

For some reason, when I set the site up orginally, it was installed in a sub-directory on the host (www.mysite.com/directory) instead of the root (www.mysite.com).  Could this be causing the problems now?  If so, why wasn't it causing problems originally?

Thanks for any help.

CJ

Ha.  This site has been a thorn in my saddle since day one.  Notsomuch becuase of DNN, but mostly becuase how the entire project was handled. We were going to host it in-house, then decided to go external.  Then the entire user and fee structure was changed while the rest of the site was still being developed.  THEN the user/fee structure has been changed AGAIN recently which caused me to have to re-code a lot of my custom registration pages.  OH, and did I mention that this was my first ever 'ground-up' DNN site deployment!? Brings a whole new meaning to 'sink or swim'. ha!

Now to the problem at-hand.  When I intinally did this site setup, I think I used the host's generic DNN installer, which put it in a folder other than the root directory for some reason.  The site is:  http://www.iowabiznet.org   You will notice that you are directed to www.iowabiznet.org/ibn for actual access to the site.

As for the aliases, I have the following listed:
* www.iowabiznet.org/ibn
* iowabiznet.org
* (devserver).netsolhost.com
* www.iowabiznet.org

I'll admit that I'm not really sure how the whole header/redirect area works with DNN.  I need to upgrade the site to the latest DNN release, so now might be the best time to move the site to the correct directory structure.

Any ideas?

Thanks Mitchel.

This isn't a top priority right now, but when I have time to really address the issue, I'll drop you a line.  The site is working just fine, but for some reason, after the hacking 'fix', now the site fires off the built-in Firefox redirect warning, which didn't occur before the 'fix'.  To get the warning, you must have "Tools -> Options -> Advanced -> 'Warn me when web site try to redirect or reload the page'" checked, which I do not have checked, but my main boss does, so it is a 'problem' for him.