Fix for "The page at https://*.sharepoint.com/* ran insecure content from http://{3rdparty_json_api_call}" error in a NAPA app


If you are receiving data through a JSONP API call from a third party service in your SharePoint 2013 NAPA app and you get an error of this pattern -
"The page at https://*.sharepoint.com/* ran insecure content from http://{3rdparty_json_api_call}"

... make the JSONP API call from its equivalent HTTPS URL i.e. replace http with https. This fix will work provided the third party API supports HTTPS.

Comments

Post a Comment

Popular posts from this blog

30+ GitHub Products & Key Ecosystem Features You Should Know in 2026

Image
GitHub has grown far beyond a place to host code — today it's an entire ecosystem covering CI/CD, AI-assisted development, security, package management, and team collaboration. Whether you're new to the platform or just want a single reference point, here's an alphabetical list of GitHub's major products and features, each linked to its official page - GitHub Actions GitHub Advanced Security GitHub Apps GitHub CLI GitHub Code Review GitHub Code Security GitHub Codespaces GitHub Container Registry GitHub Copilot GitHub Copilot Business GitHub Copilot CLI GitHub Copilot Enterprise GitHub Copilot Extensions GitHub Dependabot GitHub Desktop GitHub Discussions GitHub Education GitHub Enterprise Cloud GitHub Enterprise Server GitHub Gist GitHub Importer GitHub Innovation Graph GitHub Issues GitHub Marketplace GitHub Mobile GitHub Models  (retiring July 30, 2026) GitHub Packages GitHub Pages ...
Read more

Building a Hyderabad Weather Dashboard with the WeatherUnion API

Image
Claude recently helped a techie find his misplaced iPhone although the Find My iPhone feature was disabled by his organization's Mobile Device Management (MDM) policy.  Claude generated a Bluetooth RSSI meter in about one minute & by tracking the phone's Bluetooth signal strength he was able to locate the phone. Commenting on AI's growing role in enabling instant, bespoke software creation for immediate practical needs without traditional development, he  tweeted : " Apparently, you can just create the tool you need now. " That line stuck with me. As a weather enthusiast, I wanted a simple web app to see how the weather differs between localities in my Hyderabad neighbourhood, side by side, before deciding whether to step out. So I built it with the help of Claude & the WeatherUnion API . The visual template came from an unlikely place — ICFOSS's IoT-based Micro Climate Monitoring System for Kerala . It's a public dashboard tracking humidity, tempe...
Read more

This Week I Learned - Week 32 2026

Image
This Week I Learned -  * When unconstrained, the AI model can draw from numerous sources to assess its options on how to proceed in answering a prompt, thereby allowing widely varying outcomes. Any foundational decisions or other instructions—artifacts collectively known as “ provenance ” when properly preserved—which were formulated during the original context session and then cleared, are lost. This is the key deficiency of vibe coding which spec-driven development and context engineering seek to address. Context engineering moves a developer from a vibe coding technique to a structured approach to generating code that preserves provenance using key artifacts. This allows context to be restored by other developers, reviewed by other stakeholders, or retrieved at any point if someone wanted to audit the inputs that generated a given codebase or simply wanted to continue building upon them. Different methodologies have emerged that offer different perspectives on how to effectively...
Read more