× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Either you web server is configured to prevent GET methods or your CGI
program isn't acknowledging the GET vs the POST.
If you're using CGILIB in the xTools or CGIDEV2, they both handle either GET
or POST identically. So I'm assuming you're writing a CGI program using the
CGI APIs not one of the helper libraries.
If method equals GET, the form's data is sent via the QUERY_STRING
environment variable, if method equals POST, the form's data is sent via
standard-input. You need to use the QtmhRdStin API when POST is used, and
retrieve the data from the environment if GET is used.

-Bob Cozzi
www.RPGxTools.com
If everything is under control, you are going too slow.
- Mario Andretti

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of Shane_Cessna@xxxxxxx
Sent: Wednesday, April 20, 2005 9:24 AM
To: Web Enabling the AS400 / iSeries
Subject: [WEB400] get vs post...

I have a CGI program that's acting funny...

if I put method="get" in my <form> tag, my submit button won't 
work...however, if i change it to method="post", it works...why is this? 
Is there any reason why a method="get" would render a <input type="submit" 
value="submit"> tag useless as opposed to a method="post" tag making the 
button work?

Shane Cessna  
iSeries Programmer
iSeries WAS Administrator
North American Lighting, Inc.
(618) 662-4483 x2776
shane_cessna@xxxxxxx 



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.