Foreign commands for external utilities (and the HTTPD control functionality) will need to be assigned in the adminstration users' LOGIN.COM. Alternatives should be used when the environment supported through NETLIB. For example:
HTTPD == "$HT_EXE:HTTPD" !HTTPD == "$HT_EXE:HTTPD_NETLIB" HTTPDMON == "$HT_EXE:HTTPDMON" STREAMLF == "$HT_EXE:STREAMLF" WWWRKOUT == "$HT_EXE:WWWRKOUT" !WWWRKOUT == "$HT_EXE:WWWRKOUT_NETLIB"
Ever had to go to extraordinary lengths to find out exactly what your browser is sending to the client? The server provides a request echo facility. This merely returns the complete request as a plain-text document. This can be used for for checking the request header lines being provided by the browser, and can be valuable in the diagnosis of POSTed forms, etc.
This facility must be enabled through a mapping rule entry.
script /echo/* /echo/*
It may then be used with any request merely by inserting "/echo" at the start of the path, as in the following example.
http://wasd.dsto.defence.gov.au/echo/ht_root/
Need to locate where VMS has the HTTPd files? This simple facility maps the supplied path then parses it to obtain a resulting VMS file specification. This does not demonstrate whether the path actually exists!
This facility must be enabled through a mapping rule entry.
script /where/* /where/*
It may then be used with any request merely by inserting "/where" at the start of the path, as in the following example.
http://wasd.dsto.defence.gov.au/where/ht_root/
The Xray facility returns a request's complete response, both header and body, as a plain text document. Being able to see the internals of the response header as well as the contents of the body rendered in plain text can often be valuable when developing scripts, etc.
This facility must be enabled through a mapping rule entry.
script /Xray/* /Xray/*
It may then be used with any request merely by inserting "/xray" at the start of the path, as in the following example.
http://wasd.dsto.defence.gov.au/xray/ht_root/
This utility converts VARIABLE and VAR_? format files to STREAM_LF. The WASD HTTPd server access STREAM_LF files in block/IO-mode, far more efficiently that the record-mode required by variable-record format files. Use STREAMLF/HELP for some basic usage information.
NOTE This server can also be configured to automatically
convert any VARIABLE record format files it encounters to STREAM_LF.
15.5 - HTTPd Monitor
The HTTPd server may be monitored using the HTTPDMON utility. This utility continuously displays a screen of information comprising three sections:
The following example provides sample output:
Port: 8088 HTTPDMON v1.4.0 AXP (HTTPd v4.5) Saturday, 25-OCT-1997 16:47:36 Process: HTTPd:8088 PID: 20600467 User: HTTP$SERVER Startup: 2 Exit Status: %X00000980 (Zeroed: 1) Up: 0 08:29:46.50 CPU: 0 05:26:00.46 Pg.Flts: 50223 Pg.Used: 4% WsSize: 13968 (6984kB) WsPeak: 9968 (4984kB) AST: 4/600 BIO: 2/512 BYT: 0/146656 DIO: 0/512 ENQ: 1/600 FIL: 3/100 PRC: 0/50 TQ: 0/200 Connect: 262160 Accept: 261530 Reject: 0 Busy: 630 Current: 0 Peak: 20 Error: 0 Parse: 271655 (6631 redirect) Forbidden: 0 RMS: 8 DELETE: 0 GET: 271648 HEAD: 0 POST: 7 PUT: 0 Admin: 458 Cache: 2623 / 49243 (36) Directory: 13272 File: 115805 (37) IsMap: 1 Menu: 1 Put: 5 SSI: 6607 Update: 19828 DCL: 59234 CGI: 26612 CGIplus: 26567 (26436) Spawn: 294 Subproc: 0 1xx: 0 2xx: 251604 3xx: 73 4xx: 13227 5xx: 634 (22 errors) Rx: 24,268,949 Tx: 5,030,758,548 (bytes) Time: 25 16:39:19 Host: 131.185.250.201 Status: 200 Rx: 297 Tx: 5590 Duration: 0.601 Request: GET /ht_root/src/cgiplus/
- NOTE -
Yes! This is a genuine screen capture during an extended testing period using the WWWRKOUT utility (see 15.6 - Server Workout (stress-test)) from two other VMS systems in the same cluster. One quarter of a million requests, and 5 Gigabytes transmitted in a little over 8 hours of testing on a heavily loaded, general-purpose system! Requests comprised a mixture of file transfers, SSI documents, directory listings and CGI applications. This is an average of 9 requests per second and transfer of 160 Kbytes per second.
The /HELP qualifier provides a brief usage summary.
This information is, in part, obtained from the following logical names:
The server counter values are carried over when a server (re)starts
(provided the system has stayed up). To reset the counters use the on-line
server administration menu (see 10 - Server Administration).
15.6 - Server Workout (stress-test)
The WWWRKOUT ("World Wide Web Workout") utility exercises an HTTP server, both in the number of concurrent connections maintained and in the number of back-to-back sequential connection requests and data transfers. A native UCX image and a separate NETLIB image are provided.
This utility can be used to stress-test the WASD VMS HTTP server (or any other), or to make comparisons between it and other servers. When stress-testing a server, evaluating performance or just using it to try and break a test-bed server, it is best used from multiple, autonomous systems concurrent.
It sets up and maintains a specified number of concurrent connections to a server. It reads a buffer of data from each connection in turn, where data is waiting (does not block), until the document transfer is complete and the connection closed by the server. It then closes the local end and immediately reuses the now-free socket to initiate another sequence. If enabled (it is by default), the utility attempts to reflect the real-world in varying the data transfer rate for each connection, by setting the number of bytes read during each read loop differently for each connection. All transfered data is discarded.
The data transfer rate for each connection is displayed at connection close. It is by default it is the effective transfer rate, that is the rate from opening the connection to closing it, and so includes request processing time, etc. If the /NOEFFECTIVE qualifier is employed it measures the document data transfer rate only.
Although a single document path may be specified on the command line it is preferable to supply a range of document paths, one per line in a plain text file. Each document path and/or type specified should be different to the others, to exercise the server and file system cache. Any number of paths may be specified in the file. If the file is exhausted before the specified number of connections have been established the file contents are recycled from the first path. If a path or a file of paths is not specified the utility just continually requests the welcome document.
To assess a server's total throughput choose paths that lead to large documents (> 50K), where the overhead of connection setup, rule processing and transfer initiation are less significant than the data transfer itself. The buffer size variation functionality should be disabled using the /NOVARY qualifier when assessing data transfer rates. Responsiveness is better assessed using small documents (< 2K), where the overhead of the non-data-transfer activities is more significant.
WWWRKOUT [server_host_name[:port]] [path] [qualifiers]
Examples:
$ WWWRKOUT $ WWWRKOUT www.server.host "/web/home.html" $ WWWRKOUT www.server.host:8080 /FILEOF=PATHS.TXT $ WWWRKOUT /SERVER=www.server.host /PORT=8080 /NOBREAK /NOVARY /FILEOF=PATHS.TXT $ WWWRKOUT www.server.host:8080 /FILEOF=PATHS.TXT /NOEFFECTIVE /NOVARY $ WWWRKOUT www.server.host /FILEOF=PATHS.TXT /COUNT=500 /SIMUL=20 /BUFFER=512
The /HELP qualifier provides a brief usage summary.