Slinger Issues: POST/GET (QNX 6)

We need to use Slinger to serve data from an
embedded x86 application.

There are 2 standard HTTP methods to collect data
from a Form: POST and GET.

GET attaches the data to the URL, and historically
has had limitations on the length of data which can
be returned. It has thus been generally deprecated.

POST normally returns the data separately, and
generally has no size limit.

(!!) It is normally expected that data exceeding the size
of a GET buffer will be truncated, but QNX Slinger
crashes (terminates).

With some other OSes (e.g. Netburner), POST data
is attached to the URL, as GET data normally is, but
no size limitations are apparent.

QNX Slinger has 2 methods of calling a command
processor via the “exec” tag, “cgi” and “cmd”.
Unfortunately, the documentation is rather disorganized.

“cgi” is not adequately described, consisting mostly
of what you can’t do. “cmd” is a normal shell program,
but almost no documentation is provided.

(!!) There is no clear description in the doc on the
mechanisms of POST and GET processing for “cmd”.

(!!) For “cgi”, POST data is documented as appearing at
stdin, but no similar information is provided for “cmd”.

I tried reading from stdin in my cmd program, no data
appeared.

Anyone know anything about the problems/workings
of Slinger under QNX6?

Regards,

\

Jeff Maass jmaass@columbus.rr.com Located near Columbus Ohio
USPSA # L-1192 NROI/CRO Amateur Radio K8ND
Maass’ IPSC Resources Page: http://home.columbus.rr.com/jmaass

Hello Jeff,

The POST data is not passed to the CGI script if called from an SSI html
file. The cgi script must be called directly. If the Post data is
being passed to an SSI html file, it is procssed at that level. (see
echo, if commands)

Regards,
Dave B.


Jeff Maass wrote:

We need to use Slinger to serve data from an
embedded x86 application.

There are 2 standard HTTP methods to collect data
from a Form: POST and GET.

GET attaches the data to the URL, and historically
has had limitations on the length of data which can
be returned. It has thus been generally deprecated.

POST normally returns the data separately, and
generally has no size limit.

(!!) It is normally expected that data exceeding the size
of a GET buffer will be truncated, but QNX Slinger
crashes (terminates).

With some other OSes (e.g. Netburner), POST data
is attached to the URL, as GET data normally is, but
no size limitations are apparent.

QNX Slinger has 2 methods of calling a command
processor via the “exec” tag, “cgi” and “cmd”.
Unfortunately, the documentation is rather disorganized.

“cgi” is not adequately described, consisting mostly
of what you can’t do. “cmd” is a normal shell program,
but almost no documentation is provided.

(!!) There is no clear description in the doc on the
mechanisms of POST and GET processing for “cmd”.

(!!) For “cgi”, POST data is documented as appearing at
stdin, but no similar information is provided for “cmd”.

I tried reading from stdin in my cmd program, no data
appeared.

Anyone know anything about the problems/workings
of Slinger under QNX6?

Regards,

\

Jeff Maass > jmaass@columbus.rr.com > Located near Columbus Ohio
USPSA # L-1192 NROI/CRO Amateur Radio K8ND
Maass’ IPSC Resources Page: > http://home.columbus.rr.com/jmaass