This repository was archived by the owner on Nov 20, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 191
Rolling Notes Response Styles
loudej edited this page Nov 12, 2014
·
4 revisions
http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.4
---- passthrough
(Software MUST NOT write a body)
---- passthrough
Server transmits Transfer-Encoding header unmodified
Server transmits Response.Body bytes unmodified
(Software MUST write well-formed chunk delimiting)
---- server-chunking
Server transmits "Transfer-Encoding" header with "chunked" appended
Server transmits Response.Body bytes with chunked delimiting
---- passthrough
Server transmits "Content-Length" header unmodified
Server transmits Response.Body bytes unmodified
(Software MUST write exactly that many bytes)
---- passthrough (+close)
Server transmits "Connection" header unmodified
Server transmits Response.Body bytes unmodified
Server MUST close socket after response
When the pipeline Task is still running
---- server-chunking
Server transmits "Transfer-Encoding" header with "chunked"
Server transmits Response.Body bytes with chunked delimiting
When the pipeline Task is complete
---- passthrough
Server transmits Content-Length header
Server transmits Response.Body bytes unmodified