-
Re: Use of new CNAMEs
Sanford Whiteman Apr 6, 2017 12:55 PM (in response to Kyle Gudgeon)Please move the thread to Products and we'll continue over there. "Community" is for website feedback, not product support -- and yes, this is confusing!
-
Re: Use of new CNAMEs
Darrell AlfonsoApr 6, 2017 1:05 PM (in response to Kyle Gudgeon)
-
Re: Use of new CNAMEs
Sanford Whiteman Apr 6, 2017 1:26 PM (in response to Darrell Alfonso)Hey Darrell -- this is specific to the way Marketo deploys SSL so those posts aren't directly on-topic.
-
-
Re: Use of new CNAMEs
Sanford Whiteman Apr 6, 2017 1:24 PM (in response to Kyle Gudgeon)1. Is it possible to choose which CNAME a lp belongs to if I have domain alias set up?
Well, it "belongs" to all your CNAMEs in that it can be accessed via any of your CNAMEs.
However, as you've noticed, when an http → https redirect is necessary, it goes to your primary CNAME (i.e. the "landing page domain").
The most direct way to deal with this is to publish the page's https URL.
Short of that, you can include the original destination host in, for example, the document hash: https://about.example.com/lp.html#about. Then if a user comes in via http://about.example.com by accident and is redirected to the primary domain, you can redirect the user back to https://about.example.com.
As a complement, you can enable HSTS on the parent domain (example.com), but until you get in browsers' built-in HSTS lists there can still be the unwanted redirect. (This is the reason that anyone who isn't on HSTS preload is basically not secure.)
-
Re: Use of new CNAMEs
Kyle Gudgeon Apr 6, 2017 1:38 PM (in response to Sanford Whiteman)Thank you! I just tried again, and it looks like it just took a little time to adjust. guide.example.com/lp-123 no longer redirects to info2!
-