Use https in external links on the Yaws Web Page

Author: avtobiff

www/END2

@@ -4,8 +4,8 @@
 
 
  <p>
-      <a href="http://validator.w3.org/check?uri=referer"><img
-          src="http://www.w3.org/Icons/valid-xhtml10"
+      <a href="https://validator.w3.org/check?uri=referer"><img
+          src="https://www.w3.org/Icons/valid-xhtml10"
           alt="Valid XHTML 1.0!" height="31" width="88" /></a>
     </p>
 

www/TAB.inc

@@ -28,7 +28,7 @@ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
 <div class="%%index%%"> <a href="index.yaws" id="index" >Top Page</a> </div>
 <div class="%%configuration%%"> <a href="configuration.yaws" id="configuration">Build Config and Run</a></div>
 <div class="%%dynamic%%"> <a href="dynamic.yaws" id="dynamic" >Dynamic Content</a> </div>
-<div class="%%download%%"> <a href="http://github.com/erlyaws/yaws/releases/" id="download">Download </a> </div>
+<div class="%%download%%"> <a href="https://github.com/erlyaws/yaws/releases/" id="download">Download </a> </div>
 <div class="%%contact%%"> <a href="contact.yaws" id="contact">Contact </a> </div>
 <div class="%%doc%%"> <a href="doc.yaws" id="doc">Documentation</a>  </div>
 <div class="%%articles%%"> <a href="articles.yaws" id="resources">Articles</a> </div>

www/articles.yaws

@@ -9,34 +9,34 @@ out(_) -> {ssi, "TAB.inc","%%",[{"articles", "choosen"}]}.
 <ul>
 
 <li><p>The book <a
-href="http://shop.oreilly.com/product/0636920021452.do"><em>Building Web
+href="https://shop.oreilly.com/product/0636920021452.do"><em>Building Web
 Applications with Erlang</em></a> by Zachary Kessin, published by <a
-href="http://www.oreilly.com">O'Reilly</a> in June 2012, provides quite a
+href="https://www.oreilly.com">O'Reilly</a> in June 2012, provides quite a
 bit of information about using Yaws.</p></li>
 
 <li><p>In his "Functional Web" column in <a
-href="http://computer.org/internet/">IEEE Internet Computing magazine</a>,
-<a href="http://steve.vinoski.net/">Steve Vinoski</a> wrote a couple
+href="https://computer.org/internet/">IEEE Internet Computing magazine</a>,
+<a href="https://steve.vinoski.net/">Steve Vinoski</a> wrote a couple
 columns about Yaws. Both are available in PDF format:</p><ul> <li><a
-href="http://steve.vinoski.net/pdf/IC-Yaws.pdf">"Yaws: Yet Another Web
+href="https://steve.vinoski.net/pdf/IC-Yaws.pdf">"Yaws: Yet Another Web
 Server"</a>, July/August 2011</li> <li><a
-href="http://steve.vinoski.net/pdf/IC-SSE_with_Yaws.pdf">"Server-Sent
+href="https://steve.vinoski.net/pdf/IC-SSE_with_Yaws.pdf">"Server-Sent
 Events with Yaws"</a>, Sep/Oct 2012</li></ul></p></li>
 
-<li><p><a href="http://steve.vinoski.net/">Steve Vinoski</a> gave a talk
-entitled <a href="http://www.infoq.com/presentations/Erlang-Yaws">"Erlang
+<li><p><a href="https://steve.vinoski.net/">Steve Vinoski</a> gave a talk
+entitled <a href="https://www.infoq.com/presentations/Erlang-Yaws">"Erlang
 Web Development with Yaws"</a> at the <a
 href="https://thestrangeloop.com/archive/2012">Strange Loop 2012
 conference</a>.</p></li>
 
 <li><p>There are a number of <a
-href="http://stackoverflow.com/questions/tagged/yaws">Yaws questions with
+href="https://stackoverflow.com/questions/tagged/yaws">Yaws questions with
 answers on StackOverflow</a>.</p></li>
 
-<li><p><a href="http://steve.vinoski.net/">Steve Vinoski</a> wrote an
+<li><p><a href="https://steve.vinoski.net/">Steve Vinoski</a> wrote an
 article entitled <a
-href="http://www.infoq.com/articles/vinoski-erlang-rest">"RESTful Services
-with Erlang and Yaws"</a> for <a href="http://www.infoq.com">infoq.com</a>
+href="https://www.infoq.com/articles/vinoski-erlang-rest">"RESTful Services
+with Erlang and Yaws"</a> for <a href="https://www.infoq.com">infoq.com</a>
 back in 2008. Despite being a few years old, the advice in the article
 remains relevant.</p></li>
 

www/configuration.yaws

@@ -81,7 +81,7 @@ out(A) ->
           an install builder that is free to use free of charge
           for opensource projects.
           Get the linux installer at
-          <a href="http://www.bitrock.com/download_installbuilder_download.html">
+          <a href="https://www.bitrock.com/download_installbuilder_download.html">
             bitrock
           </a>
         </li>

www/cookies.yaws

@@ -38,7 +38,7 @@ out(A) ->
 
   <p>
     A correct definition of cookies can be found in
-    <a href="http://tools.ietf.org/html/rfc6265">RFC 6265</a></p>
+    <a href="https://tools.ietf.org/html/rfc6265">RFC 6265</a></p>
 
 
 <h2>Set Cookie</h2>

www/dynamic.yaws

@@ -177,7 +177,7 @@ out(A) ->
          box("
 [{status, 303},
  {allheaders,
-     [{header, [\"Location: \",\"http://www.funky.org/\"]},
+     [{header, [\"Location: \",\"https://www.funky.org/\"]},
       {header, [\"Set-Cookie: \",\"namn=ruler;\"]}
      ]},
  {html,\"<html> Redirected to funky.org </html>\"}

www/haxe_intro.yaws

@@ -33,11 +33,11 @@ out(A) ->
         ["The yaws_rpc module has a haXe remoting adapter that enables "
          "Yaws to respond to respond to "
          "RPC requests from a client written in ",
-         {a, [{href, "http://www.haxe.org"}], "haXe"},
+         {a, [{href, "https://www.haxe.org"}], "haXe"},
           ". haXe is a versatile open source language that compiles to "
           "Flash, Javascript and NekoVM. ",
           "For more information on haXe, visit ",
-          {a, [{href, "http://www.haxe.org/intro"}], "www.haxe.org/intro"}, "."]},
+          {a, [{href, "https://www.haxe.org/intro"}], "www.haxe.org/intro"}, "."]},
        {p, [],
         ["Implementing the server side of a haXe remoting interaction "
          "in Yaws is very similar to the one described in the ",

www/index.yaws

@@ -20,7 +20,7 @@ out(A) ->
             "another Erlang application."}}
          ]},
         {p,[], ["Yaws is entirely written in ",
-                {a, [{href, "http://www.erlang.org"}],  "Erlang"},
+                {a, [{href, "https://www.erlang.org"}],  "Erlang"},
                 ", and furthermore it is a multithreaded webserver where one "
                 "Erlang lightweight process is used to handle each client."]},
         {p,[], "The main advantages of Yaws compared to other Web technologies"
@@ -33,16 +33,16 @@ out(A) ->
         {h2,[], "erlyaws.github.io"},
 
         {p,[], ["The www page for Yaws is ",
-                {a ,[{href,"http://erlyaws.github.io"}], "erlyaws.github.io"},
+                {a ,[{href,"https://erlyaws.github.io"}], "erlyaws.github.io"},
                 ". The documentation, examples as well as releases can be "
                 "found there, and of course, ",
-                {a ,[{href,"http://erlyaws.github.io"}],"erlyaws.github.io"},
+                {a ,[{href,"https://erlyaws.github.io"}],"erlyaws.github.io"},
                 " is itself powered by Yaws."]},
 
 
         {p,[], ["Code is on : ",
-                {a,[{href,"http://github.com/erlyaws/yaws"}],
-                  "http://github.com/erlyaws/yaws"}]},
+                {a,[{href,"https://github.com/erlyaws/yaws"}],
+                  "https://github.com/erlyaws/yaws"}]},
 
         {p, [], ["Travis test results at :",
                  {a, [{href, "https://github.com/erlyaws/yaws/actions"

www/jsolait/lib/jsonrpc.js

@@ -404,7 +404,7 @@ return "["+v.join(", ")+"]";
 };
 mod.__main__=function(){
 print("creating ServiceProxy object using introspection for method construction...\n");
-var s=new mod.ServiceProxy("http://jsolait.net/testj.py",["echo"]);
+var s=new mod.ServiceProxy("https://jsolait.net/testj.py",["echo"]);
 print("%s created\n".format(s));
 print("creating and marshalling test data:\n");
 var o=[1.234,5,{a:"Hello ' \" World",b:new Date()}];

www/json_intro.yaws

@@ -40,16 +40,16 @@ out(A) ->
         ["The Yaws JSON-RPC binding is a way to have JavaScript code in the "
          "browser evaluate a remote procedure call (RPC) in the Yaws server. "
          "JSON itself as described at ",
-         {a, [{href, "http://www.json.org/"}], "http://www.json.org/ "},
+         {a, [{href, "https://www.json.org/"}], "https://www.json.org/ "},
          "is basically a simple marshaling format which can be used "
          "from a variety of different programming languages, and "
          "naturally it's completely straightforward to implement "
          "in JavaScript itself. JSON-RPC version 2.0, the version Yaws "
          "supports, is described here:"]},
        {p, [],
         [{a, [{href,
-         "http://groups.google.com/group/json-rpc/web/json-rpc-2-0"}],
-         "http://groups.google.com/group/json-rpc/web/json-rpc-2-0"}]},
+         "https://groups.google.com/group/json-rpc/web/json-rpc-2-0"}],
+         "https://groups.google.com/group/json-rpc/web/json-rpc-2-0"}]},
        {p, [],
         "The Yaws JSON-RPC implementation consist of JavaScript clients and a "
         "server side library that must be explicitly invoked by Erlang "
@@ -109,7 +109,7 @@ out(A) ->
          "function we wish to implement. Note that the first atom in the "
          "request tuple will either be 'call' or 'notification' to indicate "
          "the type of request. As per the ",
-         {a,[{href,"http://groups.google.com/group/json-rpc/web/json-rpc-2-0"}],
+         {a,[{href,"https://groups.google.com/group/json-rpc/web/json-rpc-2-0"}],
           "JSON-RPC 2.0 specification"},
          ", a 'call' is a regular request-reply while a 'notification' is a "
          "one-way message that does not have a corresponding reply."]},
@@ -156,7 +156,7 @@ box("{array, [\"foo\", \"bar\"]}"),
        {p, [],
         ["Here is yet another example, stolen from ",
          {a,
-          [{href,"http://www.redhoterlang.com/entry/ac061493b201e3d1b4490cdc3f911068"}],
+          [{href,"https://www.redhoterlang.com/entry/ac061493b201e3d1b4490cdc3f911068"}],
           "Tobbe's blog."}
          ]},
         {h4, [], "Setup the DOM"},

www/logger_mod.yaws

@@ -19,7 +19,7 @@ When Yaws is running behind a HTTP reverse proxy, the source IP of a connection
 is always the proxy's IP address. It is also this IP address that you will find
 in your log files. In this situation, it may be desirable to log the real client
 IP address by extracting it from the "<a
-href="http://en.wikipedia.org/wiki/X-Forwarded-For"
+href="https://en.wikipedia.org/wiki/X-Forwarded-For"
 target="_blank">X-Forwarded-For</a>" header.
 </p>
 

www/privbind.yaws

@@ -76,8 +76,8 @@ $ setcap 'cap_net_bind_service=+ep' /usr/lib/erlang/erts-5.7.4/bin/beam
 <p>
   There are a couple
   of other options on Linux. One is to use an auxiliary program
-  like authbind <em>http://packages.debian.org/stable/authbind</em>
-  or privbind <em>http://sourceforge.net/projects/privbind/</em>
+  like authbind <em>https://packages.debian.org/stable/authbind</em>
+  or privbind <em>https://sourceforge.net/projects/privbind/</em>
 </p>
 <p>
   These programs are run by root. Yaws writes its temporary

www/redirect.yaws

@@ -56,7 +56,7 @@ out(_A) ->
   redirects, once again, to google. Double redirects.
 </p>
 
-<p>While working with redirects, the tool <a href="http://curl.haxx.se/"> curl </a>
+<p>While working with redirects, the tool <a href="https://curl.haxx.se/"> curl </a>
 is an excellent way to troubleshoot the behaviour of your
 redirects. For example:</p>
 
@@ -76,7 +76,7 @@ redirects. For example:</p>
 
   <p>Where <tt> http://rubin.hyber.org:8000</tt> is where I am currently
     testing the <a href="redirect3.yaws"> redirect3.yaws </a> code.
-    Learn and use the <a href="http://curl.haxx.se/"> curl </a>
+    Learn and use the <a href="https://curl.haxx.se/"> curl </a>
     web client, it may not render pictures pretty, but it sure displays
     headers.
   </p>

www/redirect2.yaws

@@ -3,6 +3,6 @@
 %% redirect2.yaws
 
 out(_Arg) ->
-    L="http://www.google.com/search?num=20&hl=en&lr=lang_en%7Clang_sv&q=yaws",
+    L="https://www.google.com/search?num=20&hl=en&lr=lang_en%7Clang_sv&q=yaws",
     {redirect, L}.
 </erl>

www/server_sent_events.yaws

@@ -30,7 +30,7 @@ out(A) ->
   protocol they share.</p></li>
 
   <li><p><a href="websockets.yaws">The WebSockets protocol</a> (<a
-  href="http://tools.ietf.org/html/rfc6455">RFC 6455</a>) allows web client
+  href="https://tools.ietf.org/html/rfc6455">RFC 6455</a>) allows web client
   and server to upgrade their TCP connection from using HTTP to using some
   other protocol they agree on. The protocol they choose can be
   bidirectional and can transmit whatever data transfer formats they wish
@@ -39,7 +39,7 @@ out(A) ->
   specialized protocols, framing, and data formats to be able to
   communicate successfully.</p></li>
 
-  <li><p><a href="http://www.w3.org/TR/eventsource/">Server-Sent Events</a>
+  <li><p><a href="https://www.w3.org/TR/eventsource/">Server-Sent Events</a>
   (SSE) is a W3C working draft that unlike long polling is on a path to
   standardization and unlike WebSockets is pretty simple. Despite being a
   working draft, it's already fairly widely used. With SSE, a client sends a
@@ -102,7 +102,7 @@ out(A) ->
 
   <p>The <code>yaws_sse</code> module supplies all the SSE primitives
   required for formatting event data, event identifiers, and event retry
-  settings. See the <a href="http://www.w3.org/TR/eventsource/">Server-Sent
+  settings. See the <a href="https://www.w3.org/TR/eventsource/">Server-Sent
   Events</a> working draft for more details on using these features.</p>
 
   <p>The <code>yaws_sse</code> module also supplies functions for

www/soap_intro.yaws

@@ -50,7 +50,7 @@ out(A) ->
 
        {p,[],"To install 'erlsom' do:"},
 
-       box("git clone http://github.com/willemdj/erlsom.git\n"
+       box("git clone https://github.com/willemdj/erlsom.git\n"
            "cd erlsom; chmod a+x configure; ./configure; make\n"
            "sudo make install        # iff you want to install as root\n"
           ),
@@ -62,7 +62,7 @@ out(A) ->
            "RPC binding style. Also, only the <i>'literal'</i> encoding is supported "
            "There is no support for <i>'soap-encoding'</i>. For an explanation of the differences "
            "between these concepts, see this "
-           "<a href=\"http://www-128.ibm.com/developerworks/webservices/library/ws-whichwsdl/\">description</a>."},
+           "<a href=\"https://www-128.ibm.com/developerworks/webservices/library/ws-whichwsdl/\">description</a>."},
 
 
           {h2, [], "The SOAP client side"},
@@ -81,8 +81,8 @@ out(A) ->
         ["As an example, lets have a look at a public SOAP service that "
          "returns some weather data for the location we send to it. "
          "The WSDL specification can be found here: ",
-         {a, [{href, "http://www.webservicex.net/WeatherForecast.asmx?WSDL"}],
-          "http://www.webservicex.net/WeatherForecast.asmx?WSDL "}
+         {a, [{href, "https://www.webservicex.net/WeatherForecast.asmx?WSDL"}],
+          "https://www.webservicex.net/WeatherForecast.asmx?WSDL "}
          ]},
 
        {p,[],
@@ -135,7 +135,7 @@ out(A) ->
        box("1> inets:start().\n"
            "ok\n"
            "2> yaws_soap_lib:call(\n"
-           "      \"http://www.webservicex.net/WeatherForecast.asmx?WSDL\",\n"
+           "      \"https://www.webservicex.net/WeatherForecast.asmx?WSDL\",\n"
            "      \"GetWeatherByPlaceName\",\n"
            "      [\"Boston\"]).\n"
            "{ok,undefined,\n"
@@ -172,7 +172,7 @@ out(A) ->
        box("1> inets:start().\n"
            "ok\n"
            "2> Wsdl = yaws_soap_lib:initModel(\n"
-           "      \"http://www.webservicex.net/WeatherForecast.asmx?WSDL\").\n"
+           "      \"https://www.webservicex.net/WeatherForecast.asmx?WSDL\").\n"
            "...\n"
            "3> yaws_soap_lib:call(\n"
            "      Wsdl,\n"
@@ -220,7 +220,7 @@ out(A) ->
         ["Some final notes:",
          {ul, [],
           [{li, [],
-            "The \"http://...\" URL given as the first argument to the "
+            "The \"https://...\" URL given as the first argument to the "
             "functions above may as well be a local file, and thus written as \"file://....\". "},
            {li, [],
             "When we retrieve a HTTP located file, we will use 'ibrowse' if it exist "
@@ -248,7 +248,7 @@ out(A) ->
        box("8> Ops = yaws_soap_lib:wsdl_operations(Wsdl).\n"
            "9> {ok,Op} = yaws_soap_lib:get_operation(Ops, \"GetWeatherByPlaceName\").\n"
            "10> yaws_soap_lib:wsdl_op_address(Op).\n"
-           "\"http://www.webservicex.net/WeatherForecast.asmx\"\n"
+           "\"https://www.webservicex.net/WeatherForecast.asmx\"\n"
           ),
 
        {p,[],
@@ -258,7 +258,7 @@ out(A) ->
        box("<wsdl:service name=\"WeatherForecast\">\n"
            "  <documentation xmlns=......\n"
             "  <wsdl:port name=\"WeatherForecastSoap\".....\n"
-           "    <soap:address location=\"http://localhost:8181/WeatherForecast.yaws\" />\n"
+           "    <soap:address location=\"https://localhost:8181/WeatherForecast.yaws\" />\n"
            "  </wsdl:port>\n"
            ".....\n"
           ),
@@ -308,7 +308,7 @@ out(A) ->
            "    WeatherData =\n"
            "    #'p:WeatherData'{anyAttribs = [],\n"
            "             'Day' = \"Sunday, December 10, 2006\",\n"
-           "             'WeatherImage' = \"http://www.nws.noaa.gov/weather/images/fcicons/nfew.jpg\",\n"
+           "             'WeatherImage' = \"https://www.nws.noaa.gov/weather/images/fcicons/nfew.jpg\",\n"
            "             'MaxTemperatureF' = \"51\",\n"
            "             'MinTemperatureF' = \"28\",\n"
            "             'MaxTemperatureC' = \"11\",\n"

www/websockets.yaws

@@ -8,7 +8,7 @@ out(A) ->
 
   <p>
     WebSockets! The new kid in town! Joe
-    <a href="http://armstrongonsoftware.blogspot.com/2009/12/comet-is-dead-long-live-websockets.html">loves it</a>,
+    <a href="https://armstrongonsoftware.blogspot.com/2009/12/comet-is-dead-long-live-websockets.html">loves it</a>,
     maybe you should too?
   </p>
 
@@ -235,10 +235,10 @@ out(A) ->
       module is notified with the message <code>{close, Status, Reason}</code>,
       where <code>Status</code> is the numerical status code sent by the client
       or the value 1000
-      (see <a href="http://tools.ietf.org/html/rfc6455#section-7.4.1">RFC 6455 -
+      (see <a href="https://tools.ietf.org/html/rfc6455#section-7.4.1">RFC 6455 -
       Section 7.4.1</a>) if the client sent no status code. For an abnormal
       client closure, the status code is 1006 (as specified
-      by <a href="http://tools.ietf.org/html/rfc6455#section-7.1.5">RFC 6455 -
+      by <a href="https://tools.ietf.org/html/rfc6455#section-7.1.5">RFC 6455 -
       Section 7.1.5</a>). <code>Reason</code> is a binary containing any text
       the client sent to indicate the reason for closing the socket; this binary
       may be empty.
@@ -458,7 +458,7 @@ out(A) ->
       term <code>{fail_connection, Status, Reason}</code> is passed,
       where <code>Status</code> is the numerical status code corresponding to
       the error
-      (see <a href="http://tools.ietf.org/html/rfc6455#section-7.4.1">RFC 6455 -
+      (see <a href="https://tools.ietf.org/html/rfc6455#section-7.4.1">RFC 6455 -
       Section 7.4.1</a>) and <code>Reason</code> the binary containing optional
       information about it.
     </p>
@@ -484,7 +484,7 @@ out(A) ->
   <div class="box">
 <pre>
 %% Corresponds to the frame sections as in
-%% http://tools.ietf.org/html/rfc6455#section-5.2
+%% https://tools.ietf.org/html/rfc6455#section-5.2
 %% plus 'data' and 'ws_state'. Used for incoming frames.
 -record(ws_frame_info, {
           fin,

www/websockets_example.yaws

@@ -9,7 +9,7 @@ out(A) ->
     {content, "text/html", Body}.
 
 %% this html was copied from the basic example in
-%% http://github.com/davebryson/erlang_websocket/
+%% https://github.com/davebryson/erlang_websocket/
 html_body(WebSocketLocation) ->
 "<html>
 <head>