{"id":29993,"date":"2017-05-04T03:01:59","date_gmt":"2017-05-03T17:01:59","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=29993"},"modified":"2017-05-03T19:47:43","modified_gmt":"2017-05-03T09:47:43","slug":"ssl-web-application-primer-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/ssl-web-application-primer-tutorial\/","title":{"rendered":"SSL Web Application Primer Tutorial"},"content":{"rendered":"
\"SSL<\/a>

SSL Web Application Primer Tutorial<\/p><\/div>\n

What is your biggest friend for command line Linux text editing work, in our books … but not our pamphlettes<\/font>? The text editor vi<\/i><\/a> and for our recent SSL<\/a> work …<\/p>\n


\n<ESC> key
\ng\/http:\/s\/\/\/g
\nwq!
\n<\/code><\/p>\n

This is the level of automation enough for us, but if you are the brave type there are also Linux command line ideas where you can call on cat<\/i> and sed<\/i> ideas that we exemplify in Linux Global Substitutions Primer Tutorial<\/a>.<\/p>\n

These SSL code “conversion” thoughts should not be “glossed over” in a generic way. Take the case of our YouTube<\/a> video via its Embedded Iframe API<\/a> karaoke_youtube_api.htm<\/a> interfacing web application with this live run<\/a> link. We needed it to change in this way<\/a> for the ht<\/i>tps:\/\/<\/i> protocol, and you’ll notice in these changes that, indeed, most of the change is the usual ht<\/i>tp:\/\/<\/i> mapping to \/\/<\/i> but what about the (jQuery Ajax related) changes<\/b> …<\/p>\n


\n\/\/ code above defines (var) qsel
\nvar dprefix=\"ht\" + \"tp:\/\/www.youtube.com\/results?search_query=\";<\/b>
\nvar dp=\"ht\" + \"tp:<\/b>\/\/www.rjmprogramming.com.au\/HTMLCSS\/\";
\nif (document.URL.indexOf('ht' + 'tps:') == 0) dp=dp.replace('tp:','tps:');
\nif (document.URL.indexOf('ht' + 'tps:') == 0) dprefix=dprefix.replace('tp:','tps:');<\/b>
\n$.ajax({ url: dp + \"legend_via_map.php\",
\ndata: {\"url\":dprefix<\/b> + qsel},
\ntype: 'get',
\nsuccess: function(output) {
\n \/\/ more code
\n});
\n<\/code><\/p>\n

… where we need “other evidence”, in other words, the “scouring” of the protocol of the incoming URL (in Javascript DOM’s document.URL<\/i>) to piece together the jQuery Ajax URLs involved.<\/p>\n

Again, we recommend a client side web inspector like Firefox’s Tools->Web Developer->Inspector Console tab for this nutting out of SSL issues, the majority of which will involve a “Mixed Content” scenario, in our experience. We add one other “thought” tool to your armoury today, though. If you are like us, you will have “child” HTML iframe elements involved, and there will be right click (Windows) or two finger gesture (Mac OS X) ways to open an iframe “child” window into a new web browser tab, and this can help declutter the Web Inspector goings on for we mere mortal “tired little brains” on occasions.<\/p>\n

If this was interesting you may be interested in this<\/a> too.<\/p>\n