Skip to content
This repository was archived by the owner on Nov 20, 2018. It is now read-only.

Rolling Notes Response Styles

Jump to bottom
loudej edited this page Nov 12, 2014 · 4 revisions

Response body-related header negotiation

Server decision made after firing "OnSendingHeaders"

http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.4

Response.StatusCode 204, 304 or Request.Method HEAD

  ---- passthrough
  (Software MUST NOT write a body)

Software has set "Transfer-Encoding" ending with "chunked"

  ---- passthrough
  Server transmits Transfer-Encoding header unmodified
  Server transmits Response.Body bytes unmodified
  (Software MUST write well-formed chunk delimiting)

Software has set "Transfer-Encoding" not ending with "chunked"

  ---- server-chunking
  Server transmits "Transfer-Encoding" header with "chunked" appended
  Server transmits Response.Body bytes with chunked delimiting

Software has set "Content-Length" ---- passthrough Server transmits "Content-Length" header unmodified Server transmits Response.Body bytes unmodified (Software MUST write exactly that many bytes)

Software has set "Connection" to "closed" ---- passthrough (+close) Server transmits "Connection" header unmodified Server transmits Response.Body bytes unmodified Server MUST close socket after response

Software has done none of the above

  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
Clone this wiki locally