Quick HTTPS reverse proxy for your HTTP web service - httpsproxy2http
When your site is running with HTTPS-enabled, and tried to embed an URL or perform an API call towards external URL which is HTTP (not HTTPS), you will see the error in below:
Mixed Content: The page at 'https://ift.tt/3i6KCPB' was loaded over HTTPS, but requested an insecure resource 'https://ift.tt/384wt0N'.
This request has been blocked; the content must be served over HTTPS.
It's mean that your API call or request is somehow blocked by the browser due to https://ift.tt/3i6KCPB was loaded using HTTPS-enabled but https://ift.tt/2Bh5MKd is not. Trying to perform a call to a HTTP website from a webpage loaded via HTTPS is not allowed by browser, because it is insecure.
This simple service will help you to resolve that error. Simply change your URL from:
https://ift.tt/384wt0N
To:
https://ift.tt/2Zhrd69/your-webservice-api.com/v2/some/endpoint?param=1
In summary, use the https://httpsproxy2http.novalagung.com as the host of your destination URL, and put your actual URL as path next to it.
Disclaimer
We do not store any of your data. Use at your own risk. It's recommended to host httpsproxy2http on your own cloud.
Install httpsproxy2http in your own cloud
It's possible to setup httpsproxy2http to your own cloud. Please navigate to https://github.com/novalagung/httpsproxy2http for the details.
from Hacker News https://ift.tt/2Zhrd69
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.