Hi Eric & Sterling. > CGI POST calls will send the data you want to the CGI process. When > yo uare handling it yo umay need multiple reads to get it all... it > may not all be there when you do your first read. You'll notice that > with POST you also get some headers and one of them should tell you > how much data to expect. Therefore you can write a read loop to get > it all. > > You would most likely need to check to make sure that the port is > still open as well as read from it (copy) to deal with data transfer > delays and all. here is one such loop for reading whole POSTed data: tmp: load any [system/options/cgi/content-length "0"] buffer: make string! (tmp + 10) while [tmp > 0][tmp: tmp - read-io system/ports/input buffer tmp] > Also, decode-cgi is only for the GET request and not for POST. Yo > uwill find that POST data has a more complex structure... almost like > an email with attachments. You will have to deal with that data > yourself. That's not right. The default encoding for POST is the same as for GET, i.e. application/x-www-form-urlencoded. If you are playing with CGI in rebol, try this: http://www.rebol.cz/cgi Happy Easter, Jan -- Jan Strejcek [EMAIL PROTECTED]
