Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Fix #366 Placed anchor inside <h2> element. #435

Merged
merged 1 commit into from

2 participants

@WalterHub
Collaborator

No description provided.

@mollybostic mollybostic merged commit 5c2774a into from
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Oct 15, 2012
  1. @WalterHub
This page is out of date. Refresh to see the latest.
Showing with 5 additions and 10 deletions.
  1. +5 −10 DevCenter/dotNET/CommonTasks/enable-ssl.md
View
15 DevCenter/dotNET/CommonTasks/enable-ssl.md
@@ -17,8 +17,7 @@ This task includes the following steps:
This task will use a production deployment; information on using a staging deployment is provided at the end of this topic.
-<a name="step1"> </a>
-<h2><span class="short-header">Get an SSL cert</span>Step 1: Get an SSL certificate</h2>
+<h2><a name="step1"> </a><span class="short-header">Get an SSL cert</span>Step 1: Get an SSL certificate</h2>
To configure SSL for an application, you first need to get an SSL
certificate that has been signed by a Certificate Authority (CA), a
@@ -44,8 +43,7 @@ See [How to create a certificate for a role][].
Next, you must include information about the certificate in your service
definition and service configuration files.
-<a name="step2"> </a>
-<h2><span class="short-header">Modify svc / config files</span>Step 2: Modify the service definition and configuration files</h2>
+<h2><a name="step2"> </a><span class="short-header">Modify svc / config files</span>Step 2: Modify the service definition and configuration files</h2>
Your application must be configured to use the certificate, and an HTTPS
endpoint must be added. As a result, the service definition and service
@@ -125,8 +123,7 @@ you are using **cspack**, ensure that you don't use the
**/generateConfigurationFile** flag, as that will overwrite the
certificate information you just inserted.
-<a name="step3"> </a>
-<h2><span class="short-header">Upload to Windows Azure</span>Step 3: Upload the deployment package and certificate</h2>
+<h2><a name="step3"> </a><span class="short-header">Upload to Windows Azure</span>Step 3: Upload the deployment package and certificate</h2>
Your deployment package has been updated to use the certificate, and an
HTTPS endpoint has been added. Now you can upload the package and
@@ -152,8 +149,7 @@ certificate to Windows Azure with the Management Portal.
7. Click the **Complete** button to create your cloud service. When the deployment has reached the **Ready** status, you can proceed to the next steps.
-<a name="step4"> </a>
-<h2><span class="short-header">Connect using HTTPS</span>Step 4: Connect to the role instance by using HTTPS</h2>
+<h2><a name="step4"> </a><span class="short-header">Connect using HTTPS</span>Step 4: Connect to the role instance by using HTTPS</h2>
Now that your deployment is up and running in Windows Azure, you can
connect to it using HTTPS.
@@ -173,8 +169,7 @@ connect to it using HTTPS.
If you want to use SSL for a staging deployment instead of a production deployment, you'll first need to determine the URL used for the staging deployment. Deploy your cloud service to the staging environment without including a certificate or any certificate information. Once deployed, you can determine the GUID-based URL, which is listed in the management portal's **Site URL** field. Create a certificate with the common name (CN) equal to the GUID-based URL (for example, **32818777-6e77-4ced-a8fc-57609d404462.cloudapp.net**), use the management portal to add the certificate to your staged cloud service, add the certificate information to your CSDEF and CSCFG files, repackage your application, and update your staged deployment to use the new package and CSCFG file.
-<a name="additional_resources"> </a>
-<h2><span class="short-header">Additional Resources</span>Additional Resources</h2>
+<h2><a name="additional_resources"> </a><span class="short-header">Additional Resources</span>Additional Resources</h2>
* [How to associate a certificate with a service][]
Something went wrong with that request. Please try again.