Real scenario – Two companies are merged and portal has become common.
We are splitting DNS so Group A users lookup to one IP address and other users (Group B) see another IP, but this does mean that ALL Group A users will see the same IP, regardless of HTTP/HTTPS and this is SharePoint.
GROUP B users always look up the other IP address. GROUP B Users are authenticated thorugh TMG. http requests will be redirected to https by TMG boxes and it is served from port 80 SharePoint application.
http://my.companysite.com will be redirected to https://my.companysite.com for group B Users vis TMG
For Group A users
http://my.companysite.com – works fine
https://my.companysite.com – fails (port 443 is not configured in sharepoint)
When Group A user makes a request https://my.companyste.com, this should be redirected to http://my.companysite.com. Took the approach of adding AAM for SharePoint Webapplication and added binding to port 443. Site loads fine but there is a mix of http and https urls on the pages.
Can https://my.companysite.com can be caught and redirected to http://my.companysite.com from SharePoint?
I am thinking that the internal url should be in the same zone as the other. When I corrected it works fine. Thanks
