|Image Courtsy: http://www.software-latest.com|
Why the hell this post ....
https://. The library will rely on the current page protocol at runtime. The SSL URL is the same, only the protocol is changed:
In such situation (loading HTTP resource on HTTPS page), browsers show a warning to the user. While this warning is non-intrusive in most browsers, Internet Explorer throws the warning popup on the user's face. Adding to that the statement on the warning popup is written in the way that if users respond to the warning saying 'yes', resources loaded on HTTP are not shown.
Here is scenario in which the problem elevates itself to the highest level:
- There is an 'FBApp' that powers an iframe widget for 'Third Party Sites'.
- Best (or may be the only) page where the FBApp widget can be placed on Third Party Website is available only on HTTPS.
- To complete a transaction in FBApp widget, user must login using Facebook Login.
- Studies suggest that most of the people like to complete the transaction with FBApp in the iframe but not in a new window.
But everything can not be said in single post.......
Stay Tuned ....