Did something changed lately that would cause that to fail? Now if I use http://xxx/bla.cgi?ok I see the extension on the status line. If instead I use file:///xxx/bla.cgi?ok I only see
file:///xxx/bla.cgi on the status line and the argument are obviously now passed to. Using 0.12 GIT from may 10. Any idea? jy 2006/11/30, Jonas Fonseca <[EMAIL PROTECTED]>: > Hi, > > Jean-Yves Levesque <[EMAIL PROTECTED]> wrote Thu, Nov 30, 2006: > > Trying to see if when using local cgi scripts if > > it is possible to pass arguments. Elinks does not > > seem to accept arguments (ie blabla.cgi?test) > > > > Any other way? > > Are you sure that you have set up ELinks correctly? That is, added: > > set protocol.file.cgi.policy = 1 > set protocol.file.cgi.path = "/path/to/cgi/dir" > > to elinks.conf. > > I've added a simple test script to the elinks-0.11 version that you > can try out to see what variables (including QUERY_STRING) that ELinks > sets up. I've attached it to this message. > > Hope this helps. > > -- > Jonas Fonseca > -- Je ne parle qu'en mon nom. I am only speaking for myself. _______________________________________________ elinks-users mailing list [email protected] http://linuxfromscratch.org/mailman/listinfo/elinks-users
