W3C home > Mailing lists > Public > www-talk@w3.org > September to October 1995

Termination of POST body

From: Paul Phillips <paulp@cerf.net>
Date: Mon, 25 Sep 1995 19:42:45 -0700 (PDT)
To: www-talk@w3.org
Message-Id: <Pine.SUN.3.91.950925193337.22481A-100000@nic.cerf.net>
Netscape/X and Mosaic/X terminate POST bodies with an extra \r\n.  My 
server has been reading all data available on the socket, which means 
that the number of bytes sent to a CGI's stdin is two greater than the 
supplied content length.

The spec tells me in section 7.2.2 "... the length of that body may be 
determined in one of several ways.  If a Content-Length header field is 
present, its value in bytes represents [the length].  Otherwise, the body 
length is determined by the Content-Type (for types with an explicit 
end-of-body delimiter) [...]"

If content-length is supplied, I can use that; no problem.  If it is not, 
it appears that the "end-of-body delimiter" is the only mechanism for 
determining the end of the entity body.  This appears to be \r\n based on 
these clients' behavior.  Is this so?

Or, do all clients in normal use supply content-length, and this is a 
non-issue?

Thanks for any help,

--
Paul Phillips                                 | "Click _here_ if you do not
<URL:mailto:paulp@cerf.net>                   |  have a graphical browser"
<URL:http://www.primus.com/staff/paulp/>      |  -- Canter and Siegel, on
<URL:pots://+1-619-558-3789/is/paul/there?>   |  their short-lived web site
Received on Monday, 25 September 1995 22:42:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 27 October 2010 18:14:18 GMT