gbinghan[dev-blog]

Step 1: Getting GoDaddy SSL cert. Let's say you have a domain name of my_domain.com. You'll first need to generate the the .csr file for GoDaddy with the following command: openssl req -new -newkey rsa:2048 -nodes -keyout  my_domain.com .key -out  my_domain.com .csr This gives you 2 files: my_domain.com.key - This is the private key my_domain.com.csr - This is the Certificate Signing Request Copy the content of my_domain.com.csr file to the SSL signing authority (GoDaddy). Once approved, GoDaddy give you back a .zip file with the following 2 files: 18f1c77f369c0b59.crt - This is your cert gd_bundle-g2-g1.crt - This is the GoDaddy Certificate Chain Step 2: Convert a CERT/PEM certificate to a PFX certificate openssl pkcs12 -export -out  my_domain.com .pfx -inkey  my_domain.com .key -in 18f1c77f369c0b59.crt Step 3: Certificate to Upload to Azure. Step 4: Assign SSL Bindings. Step 5: Done! References : ...

THE PROBLEM I've deployed a REST API application ( CodeIgniter with Phil Sturgeon's Rest-Server library ) on Azure Websites. Although I've set the Access-Control-* header in my PHP application: header('Access-Control-Allow-Credentials: true'); header('Access-Control-Allow-Origin: *'); header('Access-Control-Allow-Methods: GET, POST, DELETE, OPTIONS'); header('Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept'); (If you need a working test file, here's the gist for the test file) But Azure Websites server doesn't return the headers in response. And thus all requests to the server failed with the error message: Origin http://example.azurewebsites.net is not allowed by Access-Control-Allow-Origin.   In order to make sure there's no problem with my application, I've deployed the same code to Appfog.com . And as expected, the application works just fine. The same application d...