HTTP Redirect

IRJ

We went live with a new website on a new domain yesterday. The plan was to redirect traffic to the new domain. When you enter olddomain.org, it redirects you properly to newdomain.com as it should.

I work for financial institution that uses online banking. The URL for our online banking system has been changed as well. We had an SSL certificate setup on onlinebanking.olddomain.org. My coworker setup a new SSL certificate on IIS for onlinebanking.newdomain.com. Once the site change was made I applied the new certificate to the new site and everything worked properly. However users that bookmarked onlinebanking.olddomain.org are receiving certificate errors since the cert has been applied to the new domain.

So I setup a HTTP redirect to redirect onlinebanking.olddomain.org to newdomain.com. The HTTP redirect works fine when you manually enter onlinebanking.olddomain.org. If you use the full URL https://www.onlinebanking.oldomain.org/ISuite5/Features/Auth/MFA/Default.aspx it still takes you to the old page. If you hit refresh when on the old page, it redirects to the new page properly.

Any ideas on how to get the full URL redirect working properly?

Take the Page Default.ASPX under the old onlinebanking and put a URL Direct in it (and maybe a manually link if it doesn't automatically redirect).

Also It looks like your the Redirect is just for onlinebanking.olddomain.org not onlinebanking.olddomain.org/*

IRJ

The pages of online banking are uneditable. I am not sure how the vendor has them locked down, but they are just pointers. We had to go through a hell of a process just to change the CSS for the colors of the page.

remove the pointer and then make the 404 page redirect to the new site.

IRJ

@thecreativeone91 said:

remove the pointer and then make the 404 page redirect to the new site.

This is all the APSX file says when I try to edit it. It is only 86bytes in size.

"This is a marker file generated by the precompilation tool, and should not be deleted!"

IRJ

I would also like to mention that within IIS there is only one website. It is configured to work with both domains. So in reality onlinebanking.olddomain.org and onlinebanking.newdomain.com are pulled from the same site in IIS. The only difference being that the certificate is now assigned to onlinebanking.newdomain.com.