1<html><head><title>CGI Script input</title></head><body><h1><img alt="" src="in_files/CGIlogo.gif"> CGI Script Input</h1> 2<hr> 3 4<h2>Specification</h2> 5 6For requests which have information attached after the header, such as 7HTTP POST or PUT, the information will be sent to the script on stdin. 8<p> 9 10The server will send <a href="http://hoohoo.ncsa.uiuc.edu/cgi/env.html#cl">CONTENT_LENGTH</a> bytes on 11this file descriptor. Remember that it will give the <a href="http://hoohoo.ncsa.uiuc.edu/cgi/env.html#ct">CONTENT_TYPE</a> of the data as well. The server is 12in no way obligated to send end-of-file after the script reads 13<code>CONTENT_LENGTH</code> bytes. </p><p> 14</p><hr> 15<h2>Example</h2> 16 17Let's take a form with METHOD="POST" as an example. Let's say the form 18results are 7 bytes encoded, and look like <code>a=b&b=c</code>. 19<p> 20 21In this case, the server will set CONTENT_LENGTH to 7 and CONTENT_TYPE 22to application/x-www-form-urlencoded. The first byte on the script's 23standard input will be "a", followed by the rest of the encoded string.</p><p> 24 25</p><hr> 26 27<a href="http://hoohoo.ncsa.uiuc.edu/cgi/interface.html"><img alt="[Back]" src="in_files/back.gif">Return to the 28interface specification</a> <p> 29 30CGI - Common Gateway Interface 31</p><address><a href="http://hoohoo.ncsa.uiuc.edu/cgi/mailtocgi.html">cgi@ncsa.uiuc.edu</a></address> 32 33</body></html> 34