lynx-dev
[Top][All Lists]
Advanced

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

Re: lynx-dev Re: lynxcgi vs lynxexec


From: Leonid Pauzner
Subject: Re: lynx-dev Re: lynxcgi vs lynxexec
Date: Mon, 11 Jan 1999 22:44:22 +0300 (MSK)

11-Jan-99 16:59 Aengus Stewart wrote:
> address@hidden wrote:
>>
>> >
>> > I have not quite sorted out all the problems I have had in moving our
>> > CWIS from an old machine and Lynx 2-4-2 to a new machine and Lynx 2-8-1.

>> > 2) I have the following HTML that no longer works.  lynxexec does not
>> > seem to work within ACTION only lynxcgi seems to and I get quite
>> > different behaviour.
>>
>> > "Alert!: This special URL cannot be a form ACTION!"

HTML.c have the following comment:

            /*
             *  Lynx was supporting ACTION, which never made it into
             *  the HTML 2.0 specs.  HTML 3.0 uses HREF, so we'll
             *  use that too, but allow use of ACTION as an alternate
             *  until people have fully switched over. - FM
             */

I do not know details, though.
Seems lynxcgi allowed in forms ACTION=
while lynxexec only from regular HREF=

> I am enquiring about this as I have a number of forms that call command
> line software
> via a small cgi program that creates the command lines.  With lynxexec,
> if a parameter is
> wrong or missing then the program at the command line has to deal with
> it (which is what I want) but with lynxcgi I have to deal with all
> eventualities in the cgi program, which is going to be a pain to catch
> all of these.

> Would it have been possible that my predecessor hacked Lynx 2-4-2 to get
> lynxexec to work
> or was the use of it with ACTION altered later?

Something definitely was changed since 2-4-2 :-)
Try to check CHANGES* files and grep for "lynxcgi" and "lynxexec"

Also there was a very recent changes in the development version:
1998-12-31 (2.8.2dev.13)
* Changes for handling lynxcgi:  handle failure of execve(), by showing the
  system error and then _exit()ing the child process.  Make sure REQUEST_METHOD
  is always set.  Added checks for EINTR and other errors from read() - KW



reply via email to

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