[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lynx-dev (patch) lynxcgi documentation

From: Klaus Weide
Subject: Re: lynx-dev (patch) lynxcgi documentation
Date: Mon, 8 Nov 1999 02:50:50 -0600 (CST)

On Mon, 8 Nov 1999, Philip Webb wrote:

>  lynxcgi:  is not well-described in Lynx documentation;

Quite true.

For one thing, the reader needs some knowledge of CGI in order to
use this.

But look at the man page, there is more there than in the HTML pages.

> there is nothing in Users Guide & the section in URL Support
> contains one inaccuracy & an out-of-date assumption
> that Lynx is usually installed by a system administrator.
> --- old/lynx_url_support.html Mon Nov  8 02:53:54 1999
> +++ new/lynx_url_support.html Mon Nov  8 03:05:41 1999
> @@ -566,10 +566,11 @@
>  <pre>
>        <em>lynxcgi://localhost/path_to_CGI_script</em>
>  </pre>
> -where <em>//localhost/</em> is optional and always implied.
> +where <em>//localhost</em> is optional and always implied;
> +the full path must be specified, as `~' is not recognised.

Not really.  It works without any slashes if you happen to be in the
same directory where the script resides (and execution of such a no-path
script is allowed by lynx.cfg, of course).

>  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.)
> +by Lynx.  Restrictions on acceptable paths can be imposed
> +in <em>userdefs.h</em> and <em>lynx.cfg</em>.

You cannot impose path specific restrictions in userdefs.h.  You can
only do that in lynx.cfg.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]