From cbcc3a1e1a82b01eea370bf7841e6b5f4d1e46c1 Mon Sep 17 00:00:00 2001 From: "Thomas E. Dickey" Date: Fri, 17 Oct 1997 18:00:00 -0400 Subject: snapshot of project "lynx", label v2-7-1ac_0-84 --- lynx_help/lynx_url_support.html | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'lynx_help/lynx_url_support.html') diff --git a/lynx_help/lynx_url_support.html b/lynx_help/lynx_url_support.html index 44fc6f68..d17c5c88 100644 --- a/lynx_help/lynx_url_support.html +++ b/lynx_help/lynx_url_support.html @@ -125,7 +125,8 @@ The gopher URL takes the form:
where :port is optional and defaults to :70, and the /gopher-path is opaque (not fully equivalent to the slash-separated series of symbolic elements of http paths) as explained -in RFC1738. Typically, the gopher-path consists of a gophertype +in RFC1738. Typically, the gopher-path consists of a +gophertype indicating the file or service type (e.g., 0 or I for plain text or an image, respectively, 7 for a search, or 1 for a directory), followed by a platform-specific selector. Any @@ -533,12 +534,13 @@ ACTION for a FORM, and if enabled in your Lynx image has the format:
ly nxcgi://localhost/path_to_CGI_script
where //localhost/ is optional and always implied. -The output of the script must be text/html and is rendered and displayed +The output of the script should be text/html and is rendered and displayed by Lynx. (Note that restrictions on acceptable paths can be imposed by the system administrator.)

This is a Lynxism and should be used only in local documents intended -solely for Lynx. +solely for Lynx, or for limited local testing of CGI scripts without a +http server.

On VMS, you are advised to use the threaded OSU http server, available from