|
At 08:08 27.09.2002 -0400, you wrote:
Thanks to all for the replies. Being that I am a eRPG newbie, I just determined that it would be a better exercise to learn both methods so that's why I went the GET route. I'm really not sure what the pros and cons of GET and POST are. I'm sure that the more I work on this stuff, the more clear it will become.
These are two different METHODs (<form METHOD=""> ) to send data to a CGI by means of the webserver and HTTP. GET is just adding the parameters after a question mark to the url in form variablename=value. variables are separated with &, which you should code as & when you use it in links like <a href="xxx?vara=1&varb=2">. CGIs parse these variables and their values out of environment variable QUERY_STRING. POST sends the data after the request headers. CGIs read from stdin to read the same. POST isn't limited and can send MIME conform. GET is limited to 4KB with the Original HTTP Server and to 8KB on Apache. That's, a bit simplified, the whole thing. If you are really interested, you can dive deeper by examining HTTP conversations with a tool like JunkBuster's Proxy http://www.junkbusters.org/ and reading RFCs. best regards / Mit freundlichen Grüssen Anton Gombkötö Avenum Technologie GmbH http://www.avenum.com
As an Amazon Associate we earn from qualifying purchases.
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.