Do not mix Content-Length and Transfer-Encoding headers

perplexes / m2r

Mongrel2 Connection Adapter - Ruby Encrusted Steel-Reinforced Fist

MIT License

90 stars 11 forks source link

Do not mix Content-Length and Transfer-Encoding headers #3

Closed mostlyobvious closed 12 years ago

mostlyobvious commented 12 years ago

Accroding to RFC 2616:

Messages MUST NOT include both a Content-Length header field and a non-identity transfer-coding. If the message does include a non-identity transfer-coding, the Content-Length MUST be ignored.

mostlyobvious commented 12 years ago

Reopened from topic branch in #4