[0001]
[0002]
[0003]
[0004]
[0005]
[0006]
[0007]
[0008]
[0009]
[0010]
[0011]
[0012]
[0013]
[0014]
[0015]
[0016]
[0017]
[0018]
[0019]
[0020]
[0021]
[0022]
[0023]
[0024]
[0025]
[0026]
[0027]
[0028]
[0029]
[0030]
[0031]
[0032]
[0033]
[0034]
[0035]
[0036]
[0037]
[0038]
[0039]
[0040]
[0041]
[0042]
[0043]
[0044]
[0045]
[0046]
[0047]
[0048]
[0049]
[0050]
[0051]
[0052]
[0053]
[0054]
[0055]
[0056]
[0057]
[0058]
[0059]
[0060]
[0061]
[0062]
[0063]
[0064]
[0065]
[0066]
[0067]
[0068]
[0069]
[0070]
[0071]
[0072]
[0073]
[0074]
[0075]
[0076]
[0077]
[0078]
[0079]
[0080]
[0081]
[0082]
[0083]
[0084]
[0085]
[0086]
[0087]
[0088]
[0089]
[0090]
[0091]
[0092]
[0093]
[0094]
[0095]
[0096]
[0097]
[0098]
[0099]
[0100]
[0101]
[0102]
[0103]
[0104]
[0105]
[0106]
[0107]
[0108]
[0109]
[0110]
[0111]
[0112]
[0113]
[0114]
[0115]
[0116]
[0117]
[0118]
[0119]
[0120]
[0121]
[0122]
[0123]
[0124]
[0125]
[0126]
[0127]
<!DOCTYPE html>
<html background="/wasd_root/wasdbg.gif" bgcolor="#dddddd"
text="#000000" link="#0000cc" vlink="#0000cc">
<head>
<title>Demonstrations: Miscellaneous</title>
<meta name="keywords" content="WASD, HTTPd, distribution, VMS, HTTP, freeware">
<link rel="shortcut icon" href="/favicon.ico" type="image/x-icon">
<link rel="icon" href="/favicon.ico" type="image/x-icon">
<link rel="stylesheet" type="text/css" href="/wasd_root/wasdoc/site.css">
<style type="text/css">
th { white-space:nowrap; ; }
</style>
</head>
<body>
<table cellpadding="0" cellspacing="0" border="0">
<tr><td valign="top">
<!-- the next line is an example of how to set up a link to the package -->
<a href="/wasd_root/"><img src="/wasd_root/wasdhttpd.gif" border="0" alt="Site powered by WASD and VMS"></a></td>
<td width="5%"> </td><td valign="center">
<span class="title">
Demonstrations of miscellaneous scripts and functionality.
</span>
</td></tr>
</table>
<table cellpadding="0" cellspacing="0" border="0">
<tr><td width="5%"></td><td class="caveat">
All of these should work when using the
<a href="/wasd_root/install/demo.com">DEMO.COM</a> procedure.<br>
When on an installed server some may be disabled completely or configured to
require authorization in line with local requirements.
</td><td width="5%"></td></tr>
</table>
<p>
<table class="panel" cellpadding="5" cellspacing="0" border="0" width="100%">
<tr><td class="panel1" align="left" bgcolor="#ffffff">
<table cellpadding="5" cellspacing="0" border="0">
<tr><th align="right" valign="top"><u>WOTSUP</u></th><td> </td><td>
A <a href="/wasd_root/src/utils/wotsup.c">utility</a> intended for monitoring a
WASD server in a production environment and reporting via OPCOM, email and
local-mechanism if there is a real or suspected issue with the processing.
</td></tr>
<tr><th align="right" valign="top"><u>Scréper</u></th><td> </td><td>
Can place <a href="/wasd_root/src/screper/">command-line application terminal
output into a browser</a> page. Example MONITOR script. Requires
authorisation.
</td></tr>
<tr><th align="right" valign="top"><u>Fetch HTTP</u></th><td> </td><td>
This is a <a href="/wasd_root/src/misc/fetch_example.html">command-line
utility</a> (as well as CGI(plus) script) that can be used to retrieve pages,
images, etc., from other HTTP servers.
</td></tr>
<tr><th align="right" valign="top"><u>FORMwork</u></th><td> </td><td>
Can be used to <a href="/wasd_root/src/misc/formwork_example.html">preprocess
input from an HTML form</a> and add it as a record to a CSV file and/or email
the data.
</td></tr>
<tr><th align="right" valign="top"><u>tMAILer</u></th><td> </td><td>
A drop-in CGI-based replacement for the OSU
<a href="/wasd_root/src/misc/tmailer_example.html">TMAIL utility</a> and
provides an emailing template.
</td></tr>
<form action="/echo/" method="POST">
<tr><th align="right" valign="top"><u>Echo Request</u></th><td> </td><td>
<input type="hidden" name="hidden1" value="Some hidden form data!">
<input type="hidden" name="hidden2" value="Some more hidden form data!">
Ever had to go to extraordinary lengths to find out exactly what your browser
was sending in a request? Use the <i>echo</i><sup>*</sup> facility for
both <a href="/echo/just/a/bogus/path?with&some&query&to&bulk&it&up!">GETs</a>
and
<input type="submit" value=" POSTs ">
</td></tr>
</form>
<tr><th align="right" valign="top"><u>Xray Response</u></th><td> </td><td>
The complementary facility is
<a href="/Xray/wasd_root/">Xray</a><sup>*</sup> which provides a plain-text
document containing the full response <b>header</b> and body.
</td></tr>
<tr><th align="right" valign="top"><u>Where's the Path?</u></th><td> </td><td>
The <a href="/where/wasd_root/home.html">where</a><sup>*</sup> facility
provides a mapped VMS file specification from a path!
</td></tr>
<tr><th align="right" valign="top"><u>Data Stream</u></th><td> </td><td>
The <a href="/stream/1000/">stream</a><sup>*</sup> facility
generates a quantified or unlimited stream of textual or binary data at maximum
throughput.
</td></tr>
<tr><th align="right" valign="top"><u>Content-Type?</u></th><td> </td><td>
Trouble reading a file type the server is
<a href="/wasd_root/wasdoc/env/file.unknown">not configured</a>
to recognize? Well,
<a href="/wasd_root/wasdoc/env/file.unknown?httpd=content&type=text/plain">
specify your own</a>! Here's
<a href="/wasd_root/*.*?httpd=index&type=text/plain">
<tt>WASD_ROOT:[000000]*.*</tt></a>
set up to return every file as "<tt>text/plain</tt>"!
In addition, clicking on the
<a href="/wasd_root/wasdoc/env/file.*">directory listing icon</a>
of a non-text item will return it as plain-text!
</td></tr>
</table>
<p> <i><sup>*</sup>Each of these facilities are easily enabled/disabled.</i>
</td></tr>
</table>
<p> Last revised November 2021
</body>
</html>