Re: [Technical Errata Reported] RFC7230 (4412)

The spec does allow a response like

HTTP/1.1 200 OK
Content-Type: text/plain
Transfer-Encoding: gzip
Connection: close

I tested this response with five major browsers. All of them seem to know
to consume the response body till connection EOF. ( None of them knows how
to deal with the 'gzip' encoding; and if EOF arrives prematurely resulting
in a corrupted  'gzip' body, none of them detects it as a problem. )

So it does work, sort of. Although, it seems preposterous; no server would
emit a response like that, right?

PS. If the response is "Transfer-Encoding: gzip, chunked" on a keep-alive
connection, the browsers know to demarcate the response body by chunk
framing. (Again, they don't deal with the "gzip")

Zhong Yu

Received on Thursday, 9 July 2015 18:34:13 UTC