we have app deployed heroku. think have hit wall in terms of our requirements (please make conclusion wrong ) .
it's project management app. management has decided go ssl solution hence got ourselves wildcard certificate ( *.ourapp.net) godaddy added heroku under hostname based ssl. hostname based ssl requires putting particular cname(which needs secured) pointed amazonaws url given heroku. example , if wanted secure var.ourapp.net have point cname var.ourapp.net ----> appid42352herokucom-324234.us-east-1.elb.amazonaws.com [this example url)
since wanted every first-level subdomain secure, had put *.myapp.net cname pointed amazonurl.
but interferes our application design every wildcard subdomain(basic , wildcard domains added app) needs processed such each customer branded url customername.outapp.net
currently dns handled zerigo tier one.
please suggest/recommend
sounds should work.
you added cname record: *.ourapp.com appid42352herokucom-324234.us-east-1.elb.amazonaws.com
user requests https://aclient.ourapp.com. browser follows cname, connects appid42352herokucom-324234.us-east-1.elb.amazonaws.com on port 503. server responds certificate. passes request heroku's "routing mesh". gets request https://aclient.ourapp.com, looks hostname in heroku domain configuration , finds wildcard domain app. passes request application.
Comments
Post a Comment