Title: CNAME not saving with HTTPS
Last modified: August 31, 2016

---

# CNAME not saving with HTTPS

 *  Resolved [andym3kt](https://wordpress.org/support/users/andym3kt/)
 * (@andym3kt)
 * [10 years, 3 months ago](https://wordpress.org/support/topic/cname-not-saving-with-https/)
 * This might be related to [https://wordpress.org/support/topic/https-url-1](https://wordpress.org/support/topic/https-url-1),
   but when attempted to save a custom CNAME with an HTTPS URL it only ever saves
   an HTTP version.
 * I understand that you cannot use SSL with a custom CNAME but Azure does allow
   you to reference a blob storage container with a URL that is not the *.blob.core.
   windows.net default, specifically you can do this if you are using an Azure CDN.
 * For example, I might have a blob storage account located at [https://lulua.blob.core.windows.net](https://lulua.blob.core.windows.net)
   and then an Azure CDN endpoint with a CDN profile hostname like [https://lulua.azureedge.net](https://lulua.azureedge.net).
   When attempting to enter [https://lulua.azureedge.net](https://lulua.azureedge.net)
   as the CNAME in the plugin setting it only ever saves as [http://lulua.azureedge.net](http://lulua.azureedge.net).
 * Not being able to save an HTTPS CNAME completely prohibits the use of an Azure
   CDN on an HTTPS website.
 * [https://wordpress.org/plugins/windows-azure-storage/](https://wordpress.org/plugins/windows-azure-storage/)

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Contributor [Morgan Estes](https://wordpress.org/support/users/morganestes/)
 * (@morganestes)
 * [10 years, 3 months ago](https://wordpress.org/support/topic/cname-not-saving-with-https/#post-7063778)
 * Hey [@andym3kt](https://wordpress.org/support/users/andym3kt/), the CNAME is 
   saved in the options table, but gets rewritten to `http://` on the fly to prevent
   the conflicts with the Storage SSL support. In your case when you have a Azure
   CDN with SSL support, you can bypass the URL rewrite with a filter to ensure 
   your CNAME gets used.
 * Include `add_filter( 'windows_azure_storage_allow_cname_https', '__return_true');`
   in your theme’s functions.php file or in a plugin to enable your SSL CNAME CDN(
   that’s a whole lotta letters!).
 *  [fabsenet](https://wordpress.org/support/users/fabsenet/)
 * (@fabsenet)
 * [10 years ago](https://wordpress.org/support/topic/cname-not-saving-with-https/#post-7063863)
 * this still messes up the srcset values. I would suggest to not tinker with user
   provided urls. That is really annoying.
 * Make a warning on the settings page and leave the inputs as is.
 *  [fabsenet](https://wordpress.org/support/users/fabsenet/)
 * (@fabsenet)
 * [10 years ago](https://wordpress.org/support/topic/cname-not-saving-with-https/#post-7063864)
 * nevermind, it works with the add_filter(…)
 * please make it a regular chewckbox or warning only anyway

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘CNAME not saving with HTTPS’ is closed to new replies.

 * ![](https://ps.w.org/windows-azure-storage/assets/icon-256x256.png?rev=2486101)
 * [Microsoft Azure Storage for WordPress](https://wordpress.org/plugins/windows-azure-storage/)
 * [Support Threads](https://wordpress.org/support/plugin/windows-azure-storage/)
 * [Active Topics](https://wordpress.org/support/plugin/windows-azure-storage/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/windows-azure-storage/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/windows-azure-storage/reviews/)

## Tags

 * [HTTPS](https://wordpress.org/support/topic-tag/https/)
 * [SSL](https://wordpress.org/support/topic-tag/ssl/)

 * 3 replies
 * 3 participants
 * Last reply from: [fabsenet](https://wordpress.org/support/users/fabsenet/)
 * Last activity: [10 years ago](https://wordpress.org/support/topic/cname-not-saving-with-https/#post-7063864)
 * Status: resolved