We want to setup a set of site collections that all have their own unique vanity domain names. There will be 100 or more. For example:
We are planning on using the Host-named header approach http://technet.microsoft.com/en-us/library/cc424952.aspx
However, one of the issues is how to get the web application to support both HTTP and HTTPS. My understanding of host-named header approach is you can either do one or the other, not both in the same Web Application. Plus, you lose the ability to configure anything with AAM (alternate access mappings).
One possible solution is to use UAG (Unified Access Gateway, one of the successor products to ISA) to offload all the SSL. So all unique certificates get installed at the UAG level, but what about the URLs themselves? Since AAM is not allowed with SharePoint Host Header solution, will UAG rewrite the URLs from https to http?
What is the best architecture approach?