I have a SharePoint 2010 Server Farm with 1 App server and 2 Front End servers. We are using the KEMP Load Balancer to offload SSL request that come from outside the network. We are having trouble configuring the architecture to respond to External SSL requests with the appropriate protocol. Specifically, when a user enters the external address htts://myserver.myorg.org/ without specifying the page, SharePoint responds with a 302 response. The 302 response generated by SharePoint redirects the user to http://myserver.myorg.org/default.aspx which cannot be reached from the outside since it is not https.
The Alternate Access Entries in SharePoint are as follows:
Internal URL -- Zone -- Public URL for Zone
http://myserver.myOrg.org -- Default -- http://myserver.myorg.org
https://myserver.myOrg.org -- Internet -- https://myserver.myorg.org
http://share -- Internet -- https://myserver.myorg.org
I've extended the default web application and intialized the extended web application using http://share as the header and https://myserver.myOrg.org as the public URL. When I browse to http://share from inside the network (bypassing the Kemp Load Balancer) the SharePoint server responds with an "https" address which leads me to believe that the Alternate Access Mappings are performing correctly. When I access the site from outside the network and through the kemp Load Balancer, the request seems to be routed to the default web application which responds with an "http" redirect address, rather than the extened Web Application which would respond with an "https" redirect address.
Any suggestions as to how this should be configured?