-
The book Building Web +href="https://shop.oreilly.com/product/0636920021452.do">Building Web Applications with Erlang by Zachary Kessin, published by O'Reilly in June 2012, provides quite a +href="https://www.oreilly.com">O'Reilly in June 2012, provides quite a bit of information about using Yaws.
In his "Functional Web" column in IEEE Internet Computing magazine, -Steve Vinoski wrote a couple +href="https://computer.org/internet/">IEEE Internet Computing magazine, +Steve Vinoski wrote a couple columns about Yaws. Both are available in PDF format:
Steve Vinoski gave a talk
-entitled "Erlang
+ Steve Vinoski gave a talk
+entitled "Erlang
Web Development with Yaws" at the Strange Loop 2012
conference. There are a number of Yaws questions with
+href="https://stackoverflow.com/questions/tagged/yaws">Yaws questions with
answers on StackOverflow. Steve Vinoski wrote an
+ Steve Vinoski wrote an
article entitled "RESTful Services
-with Erlang and Yaws" for infoq.com
+href="https://www.infoq.com/articles/vinoski-erlang-rest">"RESTful Services
+with Erlang and Yaws"
A correct definition of cookies can be found in - RFC 6265
+ RFC 6265There are a couple of other options on Linux. One is to use an auxiliary program - like authbind http://packages.debian.org/stable/authbind - or privbind http://sourceforge.net/projects/privbind/ + like authbind https://packages.debian.org/stable/authbind + or privbind https://sourceforge.net/projects/privbind/
These programs are run by root. Yaws writes its temporary diff --git a/www/redirect.yaws b/www/redirect.yaws index 6c5784b9b..f8336c15c 100644 --- a/www/redirect.yaws +++ b/www/redirect.yaws @@ -56,7 +56,7 @@ out(_A) -> redirects, once again, to google. Double redirects.
-While working with redirects, the tool curl +
While working with redirects, the tool curl is an excellent way to troubleshoot the behaviour of your redirects. For example:
@@ -76,7 +76,7 @@ redirects. For example:Where http://rubin.hyber.org:8000 is where I am currently testing the redirect3.yaws code. - Learn and use the curl + Learn and use the curl web client, it may not render pictures pretty, but it sure displays headers.
diff --git a/www/redirect2.yaws b/www/redirect2.yaws index 3eebf0737..0cab20f9d 100644 --- a/www/redirect2.yaws +++ b/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}. diff --git a/www/server_sent_events.yaws b/www/server_sent_events.yaws index dae844355..15e06039e 100644 --- a/www/server_sent_events.yaws +++ b/www/server_sent_events.yaws @@ -30,7 +30,7 @@ out(A) -> protocol they share.The WebSockets protocol (RFC 6455) allows web client + href="https://tools.ietf.org/html/rfc6455">RFC 6455) 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.
Server-Sent Events (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) ->
The yaws_sse module supplies all the SSE primitives
required for formatting event data, event identifiers, and event retry
- settings. See the Server-Sent
+ settings. See the Server-Sent
Events working draft for more details on using these features.
The
WebSockets! The new kid in town! Joe
- loves it,
+ loves it,
maybe you should too?
yaws_sse module also supplies functions for
diff --git a/www/soap_intro.yaws b/www/soap_intro.yaws
index 553ef7bcd..91e6b2e9e 100644
--- a/www/soap_intro.yaws
+++ b/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 'literal' encoding is supported "
"There is no support for 'soap-encoding'. For an explanation of the differences "
"between these concepts, see this "
- "description."},
+ "description."},
{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("{close, Status, Reason},
where Status is the numerical status code sent by the client
or the value 1000
- (see RFC 6455 -
+ (see RFC 6455 -
Section 7.4.1) if the client sent no status code. For an abnormal
client closure, the status code is 1006 (as specified
- by RFC 6455 -
+ by RFC 6455 -
Section 7.1.5). Reason 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 {fail_connection, Status, Reason} is passed,
where Status is the numerical status code corresponding to
the error
- (see RFC 6455 -
+ (see RFC 6455 -
Section 7.4.1) and Reason the binary containing optional
information about it.
%% 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,
diff --git a/www/websockets_example.yaws b/www/websockets_example.yaws
index 97005e6a6..19b0ac3c2 100644
--- a/www/websockets_example.yaws
+++ b/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) ->
"
diff --git a/www/yapp_intro.yaws b/www/yapp_intro.yaws
index ecdfcc48e..396072640 100644
--- a/www/yapp_intro.yaws
+++ b/www/yapp_intro.yaws
@@ -109,7 +109,7 @@ out(A) ->
[ "In order to make a \"yapp\" we need to know how to make an ordinary Erlang "
"application, that is we will need a directory layout as specified by the ",
- {a,[{href, "http://www.erlang.org/doc/design_principles/des_princ.html" }],
+ {a,[{href, "https://www.erlang.org/doc/design_principles/des_princ.html" }],
"design principles"},
" and a proper appname.app file in the ebin directory. "
"Yaws itself or yapp are standard applications and can serve as introductionary "
@@ -142,7 +142,7 @@ out(A) ->
{p,[],[
"In a similar way the yapp handler adds \"private\" opaques for a yapp "
"with the the environment variable yapp_opaque. "
- "As an example ", {a,[{href,"http://erlyweb.org/"}], "ErlyWeb "},
+ "As an example ", {a,[{href,"https://erlyweb.org/"}], "ErlyWeb "},
"applications uses both appmods and opaques in yaws.conf. These can "
"be put in the .app file instead if one makes a yapp of it:"]},
box("