Jump to content

Recommended Posts

Posted (edited)

I am currently re-developing our website and have come across some issues with getting it to go to the correct pages. On the website I have a link to go to 'Accounts' this part of the website needs to be HTTPS, so i created a IIS rewrite rule that changes this part into HTTPS. Inside this works perfectly. Unfortunately when I access the website away from my network it changes the account link to HTTP, if i type in HTTPS it works fine but the link will not auto redirect.

 

It is all under one site in IIS as i believe that is correct with a valid certificate, and bindings for both port 80 and 443,

 

if anyone else has seen this or knows why this is happening, your help would be grateful.

Edited by thesk8rjesus
Posted
After changing what I was googling I have found that the problem is down to TMG 2010 and its sending the clients round in a loop because of the URL Rewrite rule that I have. If anyone knows how to configure TMG 2010 to use URL Rewrite rules correctly, please help.
Posted

After bashing my head against my monitor, my brain started to work and i have found the solution to having a HTTP and HTTPS site through TMG2010.

 

To stop the problem of it going to HTTP i had to create a new rule stating that anything that went to /account/* would be denied and redirected to https://domain/account/*, this rule had to be higher than the HTTP allow rule.

 

I removed the URL Rewrite rule from IIS and this is now working, externally and internally.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...