Hello, After a certain URL was redirected to point to the server address of a DNN site I am administrating, I am not longer able to log in when using Internet Explorer. Firefox, however, works fine. The login problem only appears when I navigate to the site by using the new URL. The old server URL is still OK. I have been told that they used a "URL cloaking solution" to redirect the new URL to the server. Does anyone have a clue what might cause this strange problem? Thanks, Knut Erik

It's likely the URL Cloaking. I'm not familiar with that technique.

Thanks for your reply. My first thought was also that the URL cloaking causes the login problem, but I find it strange that login still works in Firefox and not in IE.

Out of curiosity, did you try clearing the cache of IE and retrying? It does seem very odd that IE would not redirect but Firefox would.

Thanks for your interest. Clearing the cache of IE does not help. Both IE and Firefox redirects correctly. It is the login link that won't work in IE. If you wish, you could try this at www.striver.no. I have created a testuser account with username: testuser and password also: testuser. Thanks, Knut Erik

Hello,

When I first loaded up Firefox it threw an error, but I was able to log in.

Using IE I could not log in.

However I did notice that when selecting any menu item that the URL remains the same, have you thought about how search engines are going to index this? could this potentially cause duplicate content issues? how can a user copy a URL for your bulletin page for instance?

I suspect it is the redirection to the same URL for all of your pages that is causing the problem.

Thanks,

Thanks for your help. The reason why this URL, www.striver.no, is being used, is that the STRIVER site has been moved from a server with a php-based system to a server with a DNN-based system, and we wanted to use the old URL to avoid confusion for the users. Therefore, an URL cloaking method was used to make the old URL point to the new server address. I'm not an expert on this, but I believe URL cloaking is a way to "hide" the real URL. I agree with you that this doesn't seem to work very well. I have been told that another option is to make a document path to the new server address and then point www.striver.no to this path. Hopefully this will work as I think it will display different URL's for different pages. Thanks again, Knut Erik

hello,

You may want to have a look at this module tutorial:
iFinity URL Master Module

it allows you to setup permanent 301 redirects.

So all you need to do is point the domain name of www.striver.no using DNS to your DotNetNuke installation files.

And then you can setup the URL master module to redirect any old PHP URLs to the correct equivalent DotNetNuke page.

Video 6 of that tutorial covers how to setup page redirections and should give you a good idea of how it works. iFinity can also provide good support on their module if you need any further tips on moving a PHP site to a DotNetNuke site.

Thanks, The iFinity module looks very interesting. Maybe just what I need. I will have to do some testing first.

Hello, I want to check if I can use the iFinity module. Can you explain a bit further what you mean by pointing the domain name to my DotNetNuke installation files? What do you mean by the installation files: Some files in particular or just the server URL for my site? Thanks.

pointing the domain name to your installation files is separate to the ifinity module setup.

Pointing the domain name to your installation files is referring to setting up your domain name to direct to the root of your DotNetNuke installation files, ie. setting the namespaces on your domain name to go to your server and then setting your server to pick up the correct domain name and go to the root of your DotNetNuke installation files using IIS. - This is your hosting setup.

Ifinity is a module which you will install to your portal once your domain name is correctly working and all the pages are displaying the correct urls for your dnn website.

Thanks for your answer. As you may recall, I already have a redirection (URL cloaking method) from the domain name of www.striver.no to the server on which the DotNetNuke site is installed, but this is no good since the same URL displays for all the site pages. Do you think I can use the iFinity module with this setup and change the URL on each page to make them differ, or do you think I will have to find another way of pointing the domain name to the DNN installation files? Also, when the redirection of the domain name is set up properly, do you think it will be possible to have URL's on the form www.striver.no/something for the site pages? Sorry for asking all these questions... Thanks

hello,

You need to setup the domain so it works as a standard domain without any URL cloaking. Once you have done that you will be able to use the iFinity module to pick up any old URLs, such as php URLS and then redirect them to any page in your DotNetNuke installation that you require - the new DotNetNuke URL will be visible, and the search engines will then index the new DotNetNuke URL and remove the old PHP URL from their listings.

It is possible to create URLs such as domain.com/something - but the setup of this is dependent on your server, Bruce Chapman over at iFinity can provide advice on the way to configure this with the iFinity module.

Hope this helps,

Thank you so much for helping me. I will first have to discuss this with the people responsible for the domain. Thanks again, Knut Erik

pppp