Title: SlideRocket Issue
Last modified: August 20, 2016

---

# SlideRocket Issue

 *  Resolved [dblinks](https://wordpress.org/support/users/dblinks/)
 * (@dblinks)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/sliderocket-issue/)
 * On domains without Sliderocket that I have forums in we have an image upload 
   capability that works seamlessly with this awesome HTTPS plugin.
 * On a single domain that we serve a few presentations in it appears that Sliderocket
   is the culprit in breaking the stated function.
 * I’d be so appreciative if there is some guidance on, and if this can be fixed.
   After reading other support issues I’m at a loss so far.
 * thx
    stu
 * console.log(‘Secure External URLs: … [http://app.sliderocket.com/app/fullplayer.aspx?id=xxxxx](http://app.sliderocket.com/app/fullplayer.aspx?id=xxxxx)
 * [WARNING] Unsecure Element: <iframe> – [http://app.sliderocket.com:80/app/fullplayer.aspx?id=xxxxxxx](http://app.sliderocket.com:80/app/fullplayer.aspx?id=xxxxxxx)
 * [http://wordpress.org/extend/plugins/wordpress-https/](http://wordpress.org/extend/plugins/wordpress-https/)

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

 *  Plugin Author [mvied](https://wordpress.org/support/users/mvied/)
 * (@mvied)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/sliderocket-issue/#post-3569982)
 * It seems as though the content is available over HTTPS, but I think I see the
   issue.
 * Try adding this to your domain mapping:
    app.sliderocket.com:80 => app.sliderocket.
   com
 * I think the plugin is checking for the validity of [https://app.sliderocket.com:80](https://app.sliderocket.com:80)
   which doesn’t work at all. Very strange that port 80 is in that URL. I’ll have
   to check for that in my code now. Thanks for reporting this.
 * Let me know if that domain mapping rule fixes it. If not, I should be able to
   get this fixed in the next release.
 *  Thread Starter [dblinks](https://wordpress.org/support/users/dblinks/)
 * (@dblinks)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/sliderocket-issue/#post-3569985)
 * Thanks, but that and a variety of iterations are a no go. Interesting that Google
   bought this company and is an app available to Google Apps users. I thought all
   their stuff was in https however….
 * On the page in question, it is in an iframe – apscnp.org/veterans-benefits/ –
   I have left your debugging feature on if you’d care to look. Absolutely every
   other page works. Great plugin Mvied.
 *  Plugin Author [mvied](https://wordpress.org/support/users/mvied/)
 * (@mvied)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/sliderocket-issue/#post-3569998)
 * They do host it all over HTTPS. The issue is the frame is coded as [http://app.sliderocket.com:80](http://app.sliderocket.com:80).
   The plugin does not blindly change every external resource to HTTPS because not
   every resource will be available over HTTPS. The plugin tests for the validity
   of the resource. In this case, when it changes the scheme to HTTPS, you end up
   with [https://app.sliderocket.com:80/](https://app.sliderocket.com:80/) which
   does not work because port 80 is specified in the URL.
 * I’ve modified my plugin to also remove the port in this case because the HTTP
   port will never be valid for the HTTPS address.
 * If you could, please give the [development version](http://downloads.wordpress.org/plugin/wordpress-https.zip)
   a shot and let me know if the issue persists.
 *  Thread Starter [dblinks](https://wordpress.org/support/users/dblinks/)
 * (@dblinks)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/sliderocket-issue/#post-3570000)
 * Sorry, I don’t see a difference but.. I restarted fpm and purged everything after
   installing your dev version (b). I am using Ngnix. This is not a huge problem
   as the content is being delivered fine, just instead of the “green” lock in the
   address bar I get the yield icon (chrome). Of course this may be an issue you
   want to continue to tackle and I will assist in any way I can. I tried this with,
   and without the mapping you indicated above.
 * Thanks Mvied,
    Stu
 *  Plugin Author [mvied](https://wordpress.org/support/users/mvied/)
 * (@mvied)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/sliderocket-issue/#post-3570003)
 * Yeah, and even when I fix this bug, you will still get those warnings because
   even if you call those slideshows over HTTPS, they load HTTP content in them.
 * I set up the same iframes in my test environment and got it fixed. Thanks for
   your help.

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

The topic ‘SlideRocket Issue’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/wordpress-https_bec2c9.svg)
 * [WordPress HTTPS (SSL)](https://wordpress.org/plugins/wordpress-https/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wordpress-https/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wordpress-https/)
 * [Active Topics](https://wordpress.org/support/plugin/wordpress-https/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wordpress-https/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wordpress-https/reviews/)

 * 5 replies
 * 2 participants
 * Last reply from: [mvied](https://wordpress.org/support/users/mvied/)
 * Last activity: [13 years, 2 months ago](https://wordpress.org/support/topic/sliderocket-issue/#post-3570003)
 * Status: resolved