TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy


Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
"Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
"Robert I. Eachus" <[log in to unmask]>
Thu, 9 Dec 1999 15:16:55 -0500
text/plain; charset="us-ascii"
"Robert I. Eachus" <[log in to unmask]>
text/plain (27 lines)
At 08:22 PM 12/8/1999 -0500, Richard L. Conn wrote:
>..."* If you are inexperience in writing server-side
>form-processing applications, choose GET.  The extra
>steps involved in reading and decoding POST-style
>transmitted parameters, while not too difficult, may
>be more than you are willing to tackle."...

    If you haven't looked at uncgi, do so.  It is a small tool which does
this decoding for you, and does several other things as well.  It is written
in very portable C, and should be easy to find on the web.  (Go to for the most recent version, currently 1.9.)  I have used it on Windows NT 4.0 with HTTPS, but I haven't tried it on Windows 95/98.

>  "* If you want to invoke the server-side application
>outside of the realm of a form, including passing it
>parameters, use GET because it lets you include form-like
>parameters as part of a URL.  POST-style applications,
>on the other hand, expect an extra transmission from
>the browser after the URL, something you can't do as
>part of a conventional <a> tag."

    Uncgi allows you to use both GET and POST in the same program invocation.   But if you do this be very careful with security issues.  Remember that anyone seeing the web page can read the text and try to use the information learned there to get creative...

                                        Robert I. Eachus

with Standard_Disclaimer;
use  Standard_Disclaimer;
function Message (Text: in Clever_Ideas) return Better_Ideas is...