We have a wildcard and this is how we deal with it: 1) Drop the www and use cfr.duke.edu.au etc. 2) Use mod_rewrite to provide redirects to ensure requests for www.cfr (etc) get seamlessly and permamently redirected to cfr (etc).
As for it.dev.duke.edu, either a new cert or a rename is necessary; itdev.duke.edu? On 9/20/07, Rick Root <[EMAIL PROTECTED]> wrote: > Okay so our IT Guy bought a wildcard certificate for *.duke.edu for > our web server today. We host numerous subdomains > > I installed the cert on https://www.cfr.duke.edu/ but it doesn't seem > to be recognized as a wildcard. > > It works though for https://cfr.duke.edu > > So obviously, the "wildcard" doesn't do what we expected it to do.. it > won't do hosts of subdomains (actually one of my web sites is > www.it.dev.duke.edu, which would be a host of a subdomain of a > subdomain!) > > What do I need to do here, besides the obvious "just buy 8 separate > certificates"? > > -- > Rick Root > Check out CFMBB, BlogCFM, ImageCFC, ImapCFC, CFFM, and more at > www.opensourcecf.com > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Get the answers you are looking for on the ColdFusion Labs Forum direct from active programmers and developers. http://www.adobe.com/cfusion/webforums/forum/categories.cfm?forumid-72&catid=648 Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:288862 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
