W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > May to August 2000

RE: CRLF on POST requests, where/how specified (repost from prior bad subject line)

From: Scott Lawrence <lawrence@agranat.com>
Date: Tue, 20 Jun 2000 13:36:45 -0400
To: "Brad Taylor" <btaylor@neonsys.com>, <http-wg@cuckoo.hpl.hp.com>
Message-ID: <005301bfdade$1a760400$954768c0@oyster.agranat.com>

See RFC 2616 ( http://www.innosoft.com/rfc/rfc2616.html#sec-4.1 )

Quoting:

----
Request (section 5) and Response (section 6) messages use the
generic message format of RFC 822 [9] for transferring entities (the
payload of the message). Both types of message consist of a
start-line, zero or more header fields (also known as "headers"), an
empty line (i.e., a line with nothing preceding the CRLF) indicating
the end of the header fields, and possibly a message-body.


        generic-message = start-line
                          *(message-header CRLF)
                          CRLF
                          [ message-body ]
----
The CRLF that separates the headers from the body is not part of
either.  Since it is not part of the body, it is not included in the
content length.

--
Scott Lawrence      Director of R & D        <lawrence@agranat.com>
Agranat Systems   Embedded Web Technology   http://www.agranat.com/
Received on Tuesday, 20 June 2000 18:40:30 EDT

This archive was generated by hypermail pre-2.1.9 : Wednesday, 24 September 2003 06:33:38 EDT