Title: Insecure content when in https
Last modified: August 30, 2016

---

# Insecure content when in https

 *  Resolved [shates](https://wordpress.org/support/users/shates/)
 * (@shates)
 * [10 years, 10 months ago](https://wordpress.org/support/topic/insecure-content-when-in-https/)
 * Hello,
 * Our blog is accessed via https but the banner image below is served via http 
   so get warnings on our page:
 * s3.amazonaws.com/plpmessages/banner5.png
 * Thanks!
 * [https://wordpress.org/plugins/pretty-link/](https://wordpress.org/plugins/pretty-link/)

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

 *  Plugin Author [cartpauj](https://wordpress.org/support/users/cartpauj/)
 * (@cartpauj)
 * [10 years, 10 months ago](https://wordpress.org/support/topic/insecure-content-when-in-https/#post-6377323)
 * This banner is only shown on the “wp-admin” side of your site, and will not affect
   the front-end, or any customer/search-engine accessible pages at all.
 *  Plugin Author [cartpauj](https://wordpress.org/support/users/cartpauj/)
 * (@cartpauj)
 * [10 years, 9 months ago](https://wordpress.org/support/topic/insecure-content-when-in-https/#post-6377444)
 * I should also have mentioned, we will be looking into this for our next release
   though. It should still use the protocol which is being used in the admin.
 *  Thread Starter [shates](https://wordpress.org/support/users/shates/)
 * (@shates)
 * [10 years, 9 months ago](https://wordpress.org/support/topic/insecure-content-when-in-https/#post-6377445)
 * Changing the URL to be “//s3.amazonaws.com/plpmessages/banner5.png” then it should
   automatically revert to the same protocol as the admin 🙂
 *  [Phil Derksen](https://wordpress.org/support/users/pderksen/)
 * (@pderksen)
 * [10 years, 8 months ago](https://wordpress.org/support/topic/insecure-content-when-in-https/#post-6377461)
 * I second this. Only insecure resource in my WP admin sites right now. Easy solution
   pointed out by [@shates](https://wordpress.org/support/users/shates/). Thanks!
 *  Plugin Author [cartpauj](https://wordpress.org/support/users/cartpauj/)
 * (@cartpauj)
 * [10 years, 8 months ago](https://wordpress.org/support/topic/insecure-content-when-in-https/#post-6377462)
 * I can confirm this will be fixed in our 2.0 release coming soon (< 2 weeks if
   testing goes well).

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

The topic ‘Insecure content when in https’ is closed to new replies.

 * ![](https://ps.w.org/pretty-link/assets/icon-256x256.png?rev=2503434)
 * [PrettyLinks - Affiliate Links, Link Branding, Link Tracking, Marketing and Stripe Payments Plugin](https://wordpress.org/plugins/pretty-link/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/pretty-link/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/pretty-link/)
 * [Active Topics](https://wordpress.org/support/plugin/pretty-link/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/pretty-link/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/pretty-link/reviews/)

 * 5 replies
 * 3 participants
 * Last reply from: [cartpauj](https://wordpress.org/support/users/cartpauj/)
 * Last activity: [10 years, 8 months ago](https://wordpress.org/support/topic/insecure-content-when-in-https/#post-6377462)
 * Status: resolved