Registered: 1348191912 Posts: 92
Reply with quote
I have installed an ISD project onto a client's IIS Server which has an SSL Certificate. Their IT Support guy is telling me I need to change my site to answer to a specific URL which ties in with the SSL certificate.
Can anyone tell me how to do this? __________________ Regards
GoalMaker Software Solutions Pty Ltd
Iron Speed MVP
Registered: 1123345706 Posts: 556
Reply with quote
Running the site under a SSL certificate should be straight forward as long as the hard work (ie installing the certificate) has been done. In its simplest form your admin guy assigns the certificate to your website and off you go, the site as such doesn't really care if its ssl or not. However you do need to bear in mind the following: Make sure all urls are relative, dont start mixing absolute urls to your own site ie http://www.mysite.com/images/image.jpg use ~/images/image.jpg or ../images/image.jpg for example. This avoids mixing ssl and non ssl stuff on the page which some browsers complain about. there is a setting in the web.config, <add key="WebServer" value="http://localhost" /> that should be set to https://..... this will ensure (check out the default.aspx page) that non sll requests are redirected to the ssl site. This stops access to the site in a non ssl way. If there is just 1 ssl cert on the site (it gets complicated if you add more than 1 to the server unless you have more than 1 nic to assign it to) its straight forward, your site matches the ssl address. If there is already a ssl cert installed and in use by another site to will have to install your site as a virtual directory or sub domain ie the cert is for mysite.com. This is already there and in use. You cant use this address as is. you may use mysubdomain.mysite.com if the ssl cert is a wild card cert and you can assign it to another nic on the server (you cant have more than 1 assigned, unlike non ssl where you can have different headers to distinguish). If its not wildcard then you could maybe (with the reassignment of the existing site) do the following. create your top level site, http://www.mysite.com and assign the cert to that level. Make sure the site is empty. Below this site create 2 virtual directories (or as many as you want to secure, sitea, siteb) This is where you place your actual site contents. you can then get to the site via https://www.mysite.com/sitea https://www.mysite.com/siteb There are other options using proxies but this should get you going. HTH __________________ Tim Titchmarsh Iron Speed Consultant MVP London UK based +44 (0)1621 835002 http://www.lightspeeditsolutions.co.uk/dotnetarchitect email@example.com firstname.lastname@example.org
Registered: 1366745851 Posts: 71
Reply with quote
Don't forget this.
h ttp ://fonts.googleapis.com/css?family=Open+Sans+Condensed:300,300italic,700 (S) ' in your master pages. That was my problem when I changed to SSL. I had to go manually change each one of the master pages. __________________ As you get older, your patience begins to wane. As a result, you become the "Grumpy Old Guy". At 60 years of age I have become this guy. I am now faced with the dilemma of an old dog learning new relationship tricks to survive.