</dt>\r
<dd>\r
<p>\r
-=== HTTP\r
+…\r
</p>\r
</dd>\r
</dl></div>\r
+<h3 id="_http">HTTP</h3><div style="clear:left"></div>\r
<div class="paragraph"><p>The HTTP interfaces in Node are designed to support many features\r
of the protocol which have been traditionally difficult to use.\r
In particular, large, possibly chunk-encoded, messages. The interface is\r
<div id="footer">\r
<div id="footer-text">\r
Version 0.1.10<br />\r
-Last updated 2009-09-12 13:07:32 CEST\r
+Last updated 2009-09-12 19:12:41 CEST\r
</div>\r
</div>\r
</body>\r
.PP
stats\.isFile(), stats\.isDirectory(), stats\.isBlockDevice(), stats\.isCharacterDevice(), stats\.isSymbolicLink(), stats\.isFIFO(), stats\.isSocket()
.RS 4
-=== HTTP
+\&...
.RE
+.RE
+.SS "HTTP"
The HTTP interfaces in Node are designed to support many features of the protocol which have been traditionally difficult to use\. In particular, large, possibly chunk\-encoded, messages\. The interface is careful to never buffer entire requests or responses\(emthe user is able to stream data\.
.sp
HTTP message headers are represented by an object like this
.RE
In order to support the full spectrum of possible HTTP applications, Node\(cqs HTTP API is very low\-level\. It deals with connection handling and message parsing only\. It parses a message into headers and body but it does not parse the actual headers or the body\. That means, for example, that Node does not, and will never, provide API to access or manipulate Cookies or multi\-part bodies\. \fIThis is left to the user\.\fR
.sp
-.RE
.sp
.it 1 an-trap
.nr an-no-space-flag 1