Title: Use https scheme
Last modified: August 22, 2016

---

# Use https scheme

 *  [archonia](https://wordpress.org/support/users/archonia/)
 * (@archonia)
 * [11 years, 6 months ago](https://wordpress.org/support/topic/use-https-scheme/)
 * Hi,
 * Is there an option to make all Cloudinary links created by the Cloudinary WordPress
   plugin use HTTPS?
    My WordPress is (only) running on HTTPS but the images are
   replaced in posts using the HTTP scheme. A quick look at the source code reveals
   it’s always using $result[“url”] instead of $result[“secure_url”].
 * Best regards,
    Chris
 * [https://wordpress.org/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/](https://wordpress.org/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/)

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

 *  Plugin Author [Cloudinary](https://wordpress.org/support/users/cloudinary/)
 * (@cloudinary)
 * [11 years, 6 months ago](https://wordpress.org/support/topic/use-https-scheme/#post-5399524)
 * Note that the code you see is relevant for Cloudinary’s migration process only
   and not for already uploaded images nor future image uploads.
    For new images
   that you wish to add to posts, you can set the ‘**Protocol**’ parameter to ‘**
   HTTPS**‘ instead of the default ‘**HTTP**‘.
 * If you wish to change already uploaded images to be delivered via HTTPS, you 
   can use 3rd party tools like [Search and Replace](https://wordpress.org/plugins/search-and-replace/),
   this plugin can go through your database and alter the URLs. So for example, 
   you can search for all `http://res.cloudinary.com/<your_cloud_name>/` and replace
   them with `https://res.cloudinary.com/<your_cloud_name>/`. Please note that you
   should backup your WordPress database **before **applying this process.
 *  [grantdb](https://wordpress.org/support/users/sixer/)
 * (@sixer)
 * [10 years, 10 months ago](https://wordpress.org/support/topic/use-https-scheme/#post-5399592)
 * Where can I change this protocol setting?
 *  Plugin Author [Cloudinary](https://wordpress.org/support/users/cloudinary/)
 * (@cloudinary)
 * [10 years, 10 months ago](https://wordpress.org/support/topic/use-https-scheme/#post-5399593)
 * This is done from within the Media library when adding a new image.
    For more
   information: [http://support.cloudinary.com/hc/en-us/articles/203636892-How-to-deliver-images-via-HTTPS-in-WordPress-](http://support.cloudinary.com/hc/en-us/articles/203636892-How-to-deliver-images-via-HTTPS-in-WordPress-)
 *  [grantdb](https://wordpress.org/support/users/sixer/)
 * (@sixer)
 * [10 years, 10 months ago](https://wordpress.org/support/topic/use-https-scheme/#post-5399594)
 * Thanks!

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

The topic ‘Use https scheme’ is closed to new replies.

 * ![](https://ps.w.org/cloudinary-image-management-and-manipulation-in-the-cloud-
   cdn/assets/icon-256x256.png?rev=2377259)
 * [Cloudinary - Deliver Images and Videos at Scale](https://wordpress.org/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/)
 * [Active Topics](https://wordpress.org/support/plugin/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/reviews/)

## Tags

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

 * 4 replies
 * 3 participants
 * Last reply from: [grantdb](https://wordpress.org/support/users/sixer/)
 * Last activity: [10 years, 10 months ago](https://wordpress.org/support/topic/use-https-scheme/#post-5399594)
 * Status: not resolved